Strange issues ....

Issue that happens:  when some users make post and upload image with it >> page loads to 'Page not found'

if you look, the post has not been added to outline but the image has been!  If you look at the page for post (for whatever module used making post) the post is there but without image ...

If some uses don't add image with posts they make the post appears on outline fine ...

^^^ from what I can tell this does not happen with all members but some! It seems to happen with several different modules ...

All members have same membership level and set allowed actions...

Any ideas please anyone ?!

anyone here know why this would happen ?

the normal response is going to be; can you duplicate this on demo.boonex.com?

 this seems to have happened lately ... I did have 2 types of membership and I deleted one  making all members 'standard'

I think this is why it's working for some users but other users are being taken to page not found ...

I don't get why when certain members try to post something with image .. the image goes to 'photos' and not on what it was posted with ... plus image shows as photo on outline but the post (for example a page) don't

If the users having issues don't try to upload images with their post >> it works as should and shows on outline

is it possible I could have effected how some modules are working for some members when I removed a membership level they may have had and returned them to standard ?

humm, so no one has come across this issue or has any ideas how I might resolve it huh?!

Normally when I see this happening it is to do with database time-outs. For some reason Dolphin then displays a page not found message. Not saying this is what's happening in your case.

 How would I test this ?  ... Database time-outs ?

 How would I test this ?  ... Database time-outs ?

if the Database was indeed timing out or whatever ... would this cause modules to not work right with certain members but ok for other members ....  I really am struggling here trying to work this out!

What I forgot to mention is that it only happens with ajax calls to the DB.

If in your case it only happens with certain members it could indicate that there are references left in the DB, maybe because of a time-out that happened when you changed the memberships (just a quess).

What I also noticed is, and this is not particular aimed at Dolphin but more a common DB setting, that memory allocated for joins is small. This in combination with the execution time-out setting gives issues as well.

Further more, Dolphin uses MyISAM for it's table spaces (which is fine for small DB's) instead of InnoDB. MyISAM outperformes InnoDB for smaller tables but it's locking method of tables is less efficient than InnoDB. Therefore, when you're DB grows you get more and more issues, like time-outs with most default hosting settings.

A tip for developers in this case is to use "LIMIT" in SQL statements. This will end the execution when the limit is reached, instead of when the end of the table is reached or a time-out occures (sometimes guilty myself of this).