[RESOLVED] Unable to install packages

Hello guys,

This one is rather strange. I've just upgraded my MODX install to 2.2RC1 and from the current PL and when I tried creating or editing a ressource, I first got the following error:

Fatal error: Call to undefined method modX::isFrontend() in /var/www/vhosts/*******/httpdocs/core/cache/includes/elements/modplugin/6.include.cache.php on line 33

Now, that error has been reported before and a as suggested in many topics, I manually cleared the cache and when I attempted installing the latest version of TinyMCE, as it seems to be causing the problem, the trouble began:

I can see a list of currently installed addons, but I can't browse for new ones. The "Download Extras from MODX" action button returns the typical confirmation dialog, but doesn't launch the package browser. I'm only left with a choice of closing it

I should also point out that while upgrading MODX, I got the following warning :

Currently, you are using the PHP suhosin extension, and your suhosin.get.max_value_length is set too low for MODX to properly compress JS files in the manager. MODX recommends upping that value to 4096; until then, MODX will automatically set your JS compression (compress_js setting) to 0 to prevent errors.

I'm not sure if this is related.

My environment:
MODX Revolution 2.2.0-rc1 / mysql 5.0.67 / php 5.2.14
Thx for any help guys [ed. note: treigh last edited this post 14 years, 10 months ago.]

For the first error, I'd recommend this:

- Manually delete all files in the core/cache directory.
- Then go to Package Manager.
- Right-click on TinyMCE and select "Remove Package".
- Repeat that until there are no TinyMCE versions shown in the grid.
- Then re-download and re-install TinyMCE.

The second error shouldn't cause any problems, but the Manager will run faster if you can fix it by either getting your host to up that value to 4096 or doing it yourself in php.ini or .htaccess (assuming that that's possible -- it depends on the server configuration).

@BobRay

Sorry for the late reply. I find this one rather strange. I've manually tried emptying the /core/cache/ directory, but the files are still there. I'm not sure the it is deleting. Do you know what might be causing this?

Thx

This issue has been resolved. After reviewing the error log, I noticed that MODX wasn`t able to connect to the package provider at http://rest.modxcms.com/extras/. The hosting company had to white list MODX package provider`s new IP address and that solved the problem.

Hi, thought I should reply to this one as this post comes up high on Google when trying to troubleshoot this error:

Currently, you are using the PHP suhosin extension, and your suhosin.get.max_value_length is set too low for MODX to properly compress JS files in the manager. MODX recommends upping that value to 4096; until then, MODX will automatically set your JS compression (compress_js setting) to 0 to prevent errors.

I've just had this exact same problem installing a MODx Revo 2.2.0-pl2 (traditional) site on a new server (Jumba - yech). Then when I logged into the Manager, the Resource Tree was not showing up at all. This bug post helped me fix it. The steps I took were:

1) Logged into the database via phpMyAdmin and opened the modx_system_settings table.

2) Found the compress_js key and manually changed it's value from 1 to 0.

3) Saved these changes then loaded up the website's file manager in cPanel.

4) Deleted the core/cache/system_settings/config.cache.php file

5) Went back to the Manager, refreshed. Huzzah... the Resource Tree is now visible!


Hope this can help someone else


Harmony

www.harmonysteel.com

Thanks Harmony,
That was causing me quite some grief!!

Thanks for the step by step Harmony.

I had the same problem with you re the "PHP suhosin extension" issue, also with a site hosted at Jumba - your instructions worked a treat.

I usually build websites in evo and am just playing with revo - not the best start! I might have gone back to evo if not for your step by step.

Thanks again.

remember, the above fix should only be needed if you dont have access to php.ini

i just had the same issue on a mediatemple hosted server, so i did exactly what the warning says & just made a blank php.ini with the recommended setting

suhosin.get.max_value_length = 4096

Thanks guys, I'm really glad my post helped


nickf08 - I was in the same boat as you about a year ago, it took some convincing to get me to switch to Revo from Evo, but I haven't looked back... it's such a great system, and if you're getting started with it now a lot of the initial bugs and usability issues have already been ironed out and the latest version is pretty awesome I hope you'll stick with Revo, it's well worth the transition pain!

[ed. note: hsteel last edited this post 14 years, 8 months ago.]

In which directory does the php.ini file go? @kn00tcn