2.2.6 package manager issue

hello,

ModX 2.2.6
Compress js and Compress css disabled in settings;
not using furls;
xampp, win7 x64, curl enabled, etc. All prev. ModX releases work on this setup;

When I use the package manager, I can browse and download packages, but when I return home, the loading screen hangs forever. A refresh shows empty package manager, but when I go back to the browser I can't download the packages because it says I already have them. They are all in my 'packages' directory, and mostly unpacked too.

Deleting from the directory, database, and clearing cache doesn't help.

Reinstalling 2.2.5, but wish I didn't have to...

Any suggestions would be very much appreciated.

-Gabriel

Just did a test - seems this might be related to a specific package, either "CodeMirror", or "Aloha". Unfortunately that's all I have time for today, but I can test tomorrow to see which one it is. But, obviously this thread is misplaced now that I have narrowed it to packages rather than the system.
If a mod' would be so kind as to delete or move it, that would be excellent, and I apologize for the inconvenience.

-Gabriel

Doesn't ring any bells, but at the very least nothing should be changed just by the presence of a transport package.

When you talk about "home", do you mean the dashboard or the package management screen?

EDIT: I've just installed both Aloha and CodeMirror on my local install, and I'm not seeing any issues whatsoever.

Usually, when Package Manager goes south, there are clues in the error log. Are you seeing anything there?

@markh : yeah, doesn't seem like it would make a difference, but I removed packages one by one from the directory and database until it worked again... Still confused, but I'm sure it's some kind of config. error on my part.

I know almost nothing about character set and collation for the database. When I install ModX I usually leave it default, but this time I chose UTF8 and UTF8_general_ci; is this something that might effect package installation? I'm grasping at straws, but that's the only thing (other than being 2.2.6 instead of 2.2.5) which is different.

Quote from: markh at Jan 01, 2013, 07:00 PM

Doesn't ring any bells, but at the very least nothing should be changed just by the presence of a transport package.

When you talk about "home", do you mean the dashboard or the package management screen?

EDIT: I've just installed both Aloha and CodeMirror on my local install, and I'm not seeing any issues whatsoever.

Hi Bob,
I wish. Error log was blank, so no help there.

Quote from: BobRay at Jan 01, 2013, 10:11 PM

Usually, when Package Manager goes south, there are clues in the error log. Are you seeing anything there?

but this time I chose UTF8 and UTF8_general_ci

That is the best option; I always install with that. It won't have any effect on package management.

Good to know, thnx.

Actually, I just noticed something that I forgot - when I created the database, I forgot to set the collation to utf8; I only did that during ModX installation... so there's probably some kind of conflict there.

Again, grasping at straws.

Quote from: sottwell at Jan 02, 2013, 01:06 PM

but this time I chose UTF8 and UTF8_general_ci

That is the best option; I always install with that. It won't have any effect on package management.

This may be useful for you: http://bobsguides.com/convert-db-utf8.html

Nice Bob! How did I miss that? I did a whole database by hand this summer. I didn't have issues with weird characters like you said in the doc, but it sure did take a long time. About 2 hours.

Next time I'll run the script. Actually, next time I'll check the db first and make sure it's set up properly. Apparently one can setup MODX with utf8 and utf8_general_ci but if the db was set to latin1 previously, you get all sorts of conflicting fields and table settings.