Originally Posted by fobicodam
Ill choose to give a chance to 2.2.6... i dont know how to tell you that.. but... its running backwards... i cant do ANYTHING whitout touching the mysql database !!! everything keeps on state "n" forever !! what did you do with this version??? i was almost happy with 2.2.4 ! The recycle bin keeps "updating" for 7 or 8 minutes ! and it doesnt delete anything !! i need to get into the phpmyadmin to delete the records manually !! i cant give THAT to my clients !!! how can i uninstall it to install the bogus but functional 2.2.4 ?????
The releases from 2.2.4 to 2.2.6 contain only bugfixes, no major changes.
The recycle can never delete records with status "n", this is the same behaviour in 2.2.4 as well. The question is why the items remain in status 'n'? If the status is not set to "" (empty), then the writeconf script has not processed the items.
In most cases, the problem is a segfault in PHP:
These segfaults seem to affect only some installations under redhat.