Error when updating to the last version

Sorry, SVN is making my life hell this morning. One file went AWOL in the release. I’m pushing up 0.9.8.2 — TBD if the WordPress repo molests it.

it’s too late for me unfortunately ??

@fireproofsocks, the changelog doesn’t say what you fixed in the 0.9.8.2 release….

Update to 0.9.8.2 worked for me (on WP 4.2.2)

Any fix on this? It sounds like you guys are still able to access your admin sections. I’m not able to.

you need to go to the plugin folder via ftp and rename the plugin folder. This will deactivate the plugin. Your site will be there again. OR you could simply download the new version manually and upload it in the folder.

Marcel: 0.9.8.2 contains the stuff that should have been in the 0.9.8 release before SVN fartbarfed on it. Sorry, when it’s hitting the fan and I know a release has broken sites I tend to skip the mundane.

I need some help with this.

I updated the plugin and my site crashed. I can’t access the website or the admin section.

I’ve gone in, renamed the plugin folder, removed the entire wordpress directory, tried a fresh install and I am still getting the error.

I even contacted GoDaddy and had them restore the last known best back up prior to updating the plugin and it didn’t fix the problem either.

Can you post a link to your website?

It’s a testing site and it’s password protected.
This is what it displays:

Warning: require_once(loader.php) [function.require-once]: failed to open stream: No such file or directory in /home/content/38/9815338/html/testing/wp-content/plugins/custom-content-type-manager/index.php on line 110

Fatal error: require_once() [function.require]: Failed opening required ‘loader.php’ (include_path=’.:/usr/local/php5_3/lib/php’) in /home/content/38/9815338/html/testing/wp-content/plugins/custom-content-type-manager/index.php on line 110

That’s also all the source code displays.

this is indeed the error that is related to the missing file. But it is not possible that a full backup PRIOR to updating the plugin would still produce this message.

Try downloading 0.9.8.2, delete every file in the plugin folder and upload the new files.

I strongly suspect that you are working on the wrong project or something. If you rename the plugin folder and you still geht this message something is not right. Maybe some caching or you have a production and a development and are working on the wrong one?

Alright, so I just went to the FTP and completely deleted the plugin directory folder and accessed the website with the same error.

I added a new plugins directory with nothing it and got the same results.
Cleared my cache, tried different browsers.

Here’s what GoDaddy had to say after doing the restore:

We have restored your content from the date specified. It appears an error is being thrown on your website of:

Fatal error: require_once() [function.require]: Failed opening required ‘loader.php’ (include_path=’.:/usr/local/php5_3/lib/php’) in /home/content/38/9815338/html/testing/wp-content/plugins/custom-content-type-manager/index.php on line 110

As the restore you requested did not correct this issue we recommend getting in touch with the plug-in provider for additional support and reviewing the link we provided above.

The only thing I can think to do is ask them to go farther back with the restore and see if that does anything.

like I said: if you delete the whole folder the file that produces the error on line 110 is not even there any more. So if you do not have any strange caching problem on WordPress side (not your Browser cache) this is not possible.

If the file is not there it cannot through out a error on its line 110 ?? that’s why I suspected you deleting on a different php account or not in the “testing” folder.

Ah. Yeah, I’m in the testing folder.

Last week, I completed deleted the entire testing folder, recreated it, downloaded a fresh install of WordPress and still couldn’t get it to work.

Thanks for your feedback.

So, I went into my PHP admin and accessed the wp_options table and my active_plugins is set to a:0:{} which means the plugins are all deactivated.

Not real sure where to go from here. Spoke with GoDaddy and they weren’t sure a back up would fix the problem based on everything I’ve already tried.

Anyone else got any ideas?