ProSam

Any help would be appreciated.

@placeman you rock. I had no idea. Thank you. This is my clients account so I had to go based on what he told me. Logging in now to make the changes

Yeah I just verified. GoDaddy is running PHP Version 5.2.17

@placeman

I do not have control of what version of PHP godaddy installs on their servers.

2.5.1 is not working on GoDaddy server.

@tonyhebert

I provided a link to download 2.4.1 above your comment. Download, remove 2.5 and upload 2.4.1 and you should be good to go.

@diego Battistella

El plugin no tiene nada que ver con la base de datos, no se supone que hubieses perdido todos los eventos. Si borras el plugin 2.5 y subes el 2.4.1 que yo enlace arriba.

Removed the latest version (2.5) from the broken site and downloaded/installed the previous version (2.4.1) of the plugin from the other site and we are now good to go on both sites. Download 2.4.1

@codemovement.pk

That link is broken and says facebook

@codemovement.pk

We are running WordPress 4.5.2, this is the issue.

All-in-One Event Calendar Version 2.4.1 is running just fine on one of my other WP sites with no issues on WP 4.5.2. I’m in the process of copying 2.4.1 over to my other sites to get the calendar up and running until the developers gets this fixed.

@codemovement.pk

I have installed above plugin to replicate the issue but it’s working fine. I suggest that rename the ‘all-in-one-event-calendar’ from ftp and download plugin to upload to plugin folder. Hope this would solve the issue.

There’s something wrong with the latest version of the plugin. It has nothing to do with renaming the folder and uploading a fresh version. I tried that, it did not work.

Oh, wait. I’m dumb. I found it. Sorry. It’s in the theme settings in customization.

Anyone?

I just took a look at the DB and nothing is recorded in the wp-donations table.

I’m having this same problem.

Ever since the upgrade to 2.8.6 my permalinks broke. I made no changes other than to upgrade.

Turning off permalinks fixes it but my url’s are all wrong.

My .htaccess file is chmodded to 666

And it looks like this

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /blog [L]
</IfModule>
# END WordPress

I have several versions of WP running on different sites and the plugin worked flawlessly in ver. 1.5.2 but not at all in ver. 2.6.2, so I can only deduce that this is a compatibility issue. Something in the new version of WP is not playing nice with this plugin