CMS Made Simple Forums

The following debug information was displayed during a part of the 1.9.4.3 to 1.10 upgrade:

Debug: (8.000000000008E-6) - (usage: 13572672) - (peak: 13710152)
Current-version: 0.7
Debug: (0.095959) - (usage: 13974464) - (peak: 14342216)
Current-version: 0.7
Debug: (0.224853) - (usage: 17655496) - (peak: 18033080)
Current-version: 0.7

and

We expected some results to be available from queued operations, but none were found. Please try to reproduce this experience, and provide sufficient information to support personell for diagnoses (Troubleshooting)

error occurred after the core was successfully upgraded, and during the usage of the module manager when modules where upgraded afterwards. (Frontend users or CGExtensions)

No problems detected afterwards, modules where upgraded correctly.

with regards

Marc

I get "We expected some results to be available from queued operations, but none were found. Please try to reproduce this experience, and provide sufficient information to support personell for diagnoses" whenever I use the module manager to upgrade a module, but it seems to upgrade fine anyway.

Not a solution to your problem... just a little moral support, in that I've seen one of your errors on my install as well.

I've had that too, after successfullly upgrading to 1.10 when upgrading some modules later. The upgrades all seem to be successful so not sure what it all means!

Are you still experiencing this? I too am getting the same notice when I upgrade any module (most recently FEU to 1.16.4) on CMSMS 1.10.1. The modules seem to be upgrading ok but I get that disconcerting notice each time.

I have had this error as well: "We expected some results to be available from queued operations, but none were found. Please try to reproduce this experience, and provide sufficient information to support personell for diagnoses"

It occurred on several sites after upgrading them from 1.9.4.2 to 1.10.1. The error occurred when upgrading several modules.

It just happened again when I installed an earlier version of TinyMCE in order to troubleshoot another issue and then upgrading that version from within Module Manager to the latest version.

I also notice that clicking on the Troubleshooting link on the error page leads to another page http://wiki.cmsmadesimple.org/index.php ... leshooting on which there is no information to actually assist in troubleshooting.

I've had it again too in a successful upgrade from 1.9.4.2 to 1.10.1.

I just ignore it now. I don't upgrade TinyMCE (if I intend using it for a particular site) - I delete the old module before upgrading then install the latest version from Module Manager.