Please check configuration and save in order to use JEvents

[MrVirtual]

is it maybe the php settings;

http://i.imgur.com/hj9Ky.png

[Tonyp]

500 is normally a permissions error.

I would switch Register Globals off in PHP as it can be a security issue. So unless you have some thing asking for it?

Also, Can you install Akeeba Admin tools and check use the fix permissions and database tool.

[Paz]

Greetings,

I'm having the same problems. Have tried cleaninstall.php. PHP settings are correct and identical to according to the posted jpg. Have also used Akeeba Admin tools to fix permissions.

I keep saving the config and end up back with the message: "Please check configuration and save in order to use JEvents"

Im on j1.7.3, php 5.3.8

Can you offer advice please?

[Tonyp]

hi paz,

if you wish I can take a look for you? pm me your admin username and password with the site url.

Regards
Tony

[andser]

Guys,

Is there a fix for this strange behaviour?

I can see in my logs every time I hit Save button:

PHP Warning: constant(): Couldn't find constant JPATH_ in /var/www/vanilla/web/libraries/joomla/installer/adapters/module.php on line 115, referer: http://vanilla.local/administrator/inde ... iew=manage

[andser]

Guys,

Is there a fix for this strange behaviour?

I can see in my logs every time I hit Save button:

PHP Warning: constant(): Couldn't find constant JPATH_ in /var/www/vanilla/web/libraries/joomla/installer/adapters/module.php on line 115, referer: http://vanilla.local/administrator/inde ... iew=manage

Perhaps this will help someone:

1. Uninstall component
2. Uninstall all modules
3. Uninstall all plugins
4. Drop all jev tables (be careful)
5. Disable all referencing menu items in your menus
6. Run cleaninstall.php
7. Delete jevents folders (in my case I had leftovers in plugin and images)
8. Clean-up joomla caches
9. Logout
10. Clean-up browser caches
11. Login
12. Install component

Viola! - Back in business

(Of course I do not take responsibility for any damage blah, blah...)

[Geraint]

that is a strange one - it looks as though you may have an admin module that has not set the client attribute somehow.

If the probelm arises again for some reason - please report back