To Do list -- Bug fixes for new site.

[melott]

Hi....

I've scaned thru the posts here and haven't seen
PMail mentioned.

It would be nice to have the PMail letters back in the
user menu to tell when you have unread PMail waiting.

It would be nice to have the PMail letters back in the

It's already there.  When you get a new message, it puts the number in brackets next to your inbox (and I believe puts it in bold).  The rest would involve serious code hacking.

Wayne

That's as clear as the local tap water (which is often quite cloudy)

Ok, let me see if I can help run it through a Brita filter for ya.

"Notify at next login" sets a flag in the system which -- when you log in next -- checks to see if you have new notification mail.  

The Amiga browsers for some strange reason keep dropping the session information incorrectly.  This means we had to install a "auto-login hack" (the remember me button).  What that does is to use cookies to reset the session every time you visit the site, keeping you logged in for one full week at a time.  

Since you're automatically logged in and don't actually go through the actual login process each time you visit the site, the "trigger" which says "check for new notifications when I log in" is never executed, hence it doesn't work the way you want it to.  Sorry, them's the breaks.

Wayne

[T_Bone]

Strange, not sure if this is a bug or if I've hit some preset per-day posting limit.... :-P

I can't post in Talk About, when I submit a reply to a thread where I was clearly right :-P and on the verge of converting KennyR to a Capitalist, I got a message that said I wasn't allowed to post to that forum. Then when I listed the thread, the Reply buttons on all posts were missing. Looked through Talk About, and it was the same for all threads, but I can post outside of Talk About.

Is this a per-forum cap that I hit?

[T_Bone]

...er... nevermind.

I think you just moved the forum from underneath me...

I went to look for that thread again, and it was GONE! So I went to View Account to see if I could still link to it, and it linked right to the thread, but in a CoffeeHouse form!

COOL! Disregard the above:-)

[Framiga]

Hi,

a new problem here, XOOPS related.

If i try to :

-Login

-Reply to a post

-edit a post

-Update my account

i have the following messages:

"The requested document contain no data" (IBrowse 2.3)

with javascript error log enabled:

"Type error on line 28 of function xoopsValidate Wrong type of object for operation"

and

"Type error on line 1 Wrong type of object for operation"

No problems with other XOOPS based sites.

Ciao

PS- as you can see, the post is sent anyway but . .  .

URL and cookies www.amiga.org as usual

EDIT- found a similar JS error on AW (due i've never enabled JS log before) BUT all the operations, go OK . . . .here i must to reload the AOrg main page to see my post, reply, updated profile and so

So, EVERYONE WHO HAS SEEN THE PROBLEM....  Is it only related to IBrowse 2.3?  Is this the latest version?  Is it a new version that you're using?  We're trying to isolate the problem with duplicate posting, and almost everyone who's complained about it is talking IBrowse 2.3, except for one IE user.  

[Ryu]

im told the same problems are occuring on some mozilla based browsers too, though im told it works in opera...

The ONLY change that we have made yesterday is to add a CSS default font to help clean up the site for those who're running CSS compatible browsers (most of you).  As such, the search for the source of this problem continues, as everything with the DB currently appears to check out ok (reporting status ok on a check).

Wayne

[Framiga]

PAY ATTENTION

FOUND A VIRUS

"HappyNewYear 96'"

Present in the Resore2003 package sent to some of us with some eye-candy IB2.3 related.

Birdie

MagicMenu and MagicMenuPrefs

and /Mui/Images/Kmel/Kmel_knob2.image

The same virus is present in "GlassAmiga.lha" and GlassAmigaV2.lha" archives. (same files)

Ciao

[Framiga]

Hi

i'm now on Voyager 3.3.126 68K and works fine (the same on AWeb 3.4
APL).

Anyway, those problem with Ibrowse 2.3, begun from yestrerday in the
morning (GMT +100 or during the night .  .i don't know).

Virus removed (/mui/images/kmel/kmel_knob2.image = HappyNewYear 96')
even if, i' dont think it was the problem here.

As already said, other XOOPS based sites, works OK.

Cheers

[futaura]

I think I can tell you exactly why the problem is occurring with IBrowse.  When posting form data, IBrowse always terminates the form data in the HTTP request with a CRLF (AWeb does not).  In this case, the amiga.org server does not bother to send a HTTP response back, hence the error message from IBrowse.  Having changed IBrowse to not send the CRLF after the form data, the problem went away completely.

So, it seems that the xoops scripts do not handle this.  Also, were there any changes to the server or php versions? Apparently, some servers don't bother passing the trailing CRLF onto the script anyway, so that could also explain why xoops had no problem before, but does now (assuming the xoops scripts haven't changed in the way they handle this.

I'm not 100% sure (yet) whether this should be made a permanent change in IBrowse - clearly, there must have been a reason for sending the CRLF for all these years :-)  And it's quite possible IBrowse does because other browsers do the same (or did do in earlier versions).

Thanks very much for your assistance.  I've e-mailed the guys who actually wrote Xoops and I'm waiting on them to get a chance to look at it.  Your input may be very helpful indeed.

Wayne

[Framiga]

Hi futaura

thanks a lot for the reply. :-)

 . .  .but 2 days ago, all runs perfectly here.

Cheers

[uncharted]

Hey wayne

very recently I've started to have tiny problems on the forums.  I get a small amount of junk text above the banner when reading the forums (no other time). This is also coupled with an error after the page has loaded (saying that the page hasn't loaded).  I use Safari 1.0 on MacOS 10.2.8.

The junk text on this forum says "210 [c sSf ])                  
"

if that is any help.

it only occurs when reading forums, not posting or on any other module.

That's very odd indeed.  Almost as though your browser doesn't support basic HTML comments.

Wayne