New events don't get saved

[Wojciech]

Hello! I’ve followed all the suggestions I got from you guys through FB:
– Make sure you’re running the latest version of WordPress. YES
– Make sure you’re running the latest version of the Events plugin (2.0.8) and the Events PRO plugin (2.0.8 again). YES
– It could be a permalinks-related issue. Resave your permalinks page to reset them. If you have permalinks turned off, turn them on with a structure like /%postname%/. DID THAT
– Switch to a different templating option under Settings –> The Events Calendar, using the dropdown. TRIED ALL
– Try increasing the PHP memory for your website: http://www.dailyblogging.org/wordpress/increase-wordpress-memory-limit/ ADDED THE CODE TO wp-config.php
– Try the plugin deactivation route: deactivate your other plugins one-by-one, until just The Events Calendar/PRO are active, to see if it’s a conflict on that end. NO OTHER PLUGINS ACTIVE – THIS IS A FRESH INSTALL OF WP
– If that doesn’t do the trick, is there a staging environment where you can test all plugins off (except Events) AND reverting to the default 2011 theme? SEE ABOVE

So that was on the free version. Just purchased the PRO version in hopes of some miracle…

… no miracle here 🙁
I have a feeling this is database permission related… why else wouldn’t the plugin be able save its data? The rest of the post gets saved (title, description, category).

HEEEEEELP!

[Wojciech]

Ok. Update.

The problem site is on some host I have no control of in Poland. The WP is in polish, although I don’t suspect that’s the issue here.

I have just installed a fresh copy of WP on goddady (on an account I already have) and everything is running peachy. So bonus points if you can figure out what exactly is going on on the first server (it’s in the ticket).

Cheers.

[Barry]

That’s interesting. It’s difficult to say however just by looking at the front end of the website. One thing I might suggest, regarding the PHP memory limit, is that you create a file containing the following code:

And nothing else.

Save it as phpinfo.php or something similar and then view it via your web browser – you should see a load of data about your PHP set-up and you might want to confirm here that the memory limit has indeed been raised (it’s possible that the host does not actually allow the memory limit to be raised, in which case the code you added will be ineffective).

What you would be looking for here is an entry marked memory_limit and if it is at 32M, 64M or higher then we should be ok on the memory front, however it could be worth checking.

[Barry]

… Hmm, code doesn’t format too nicely in the forum. See this Pastebin snippet instead: http://pastebin.com/hvNmBNfZ

[Barry]

Hi Wojciech – how are you getting on here?

[Author]

Posts