Log in | Register
  1. Forum
  3. Discontinued Products
  5. JFBConnect Joomla 2.5 Support (CLOSED)
  7. Updating JFBConnect completely destroyed website

Topic-icon Updating JFBConnect completely destroyed website

Active Subscriptions:

None
13 years 1 month ago #32819 by severewx
While doing the automatic update, an error appeared and to my shock I discovered that index.php in the administrator folder was completely erased, leaving only a blank index.php.

Any ideas?!?!?!
The topic has been locked.
Support Specialist
13 years 1 month ago #32828 by alzander
That's not a problem we've ever heard of before. Joomla even has safeguards in place which won't let a component installation update folders outside of the /components, /modules, /libraries, or /plugins directory, so I'm not sure how JFBConnect did that.

JFBConnect itself (the main component) can not be upgraded from the Update Manager. It can only be upgraded by going into the component itself. When you try it from the Update Manager, you'll simply see an error that the installation failed, but no changes are made to the system during the process.

All the add-ons for JFBConnect (modules, plugins, etc) can be upgraded from the update manager though.

Can you tell me:
* All the extensions that you were trying to update when the problem happened?
* What was the error message you got?
* When you say the index.php file is empty, do you mean your home page is just blank or if you edit that actual file, it's completely blank?
** If the home page is just white/blank, try going into the Global Configuration area of Joomla and set error reporting to "Maximum" and see if a better message appears.
** If the index.php file is actually empty when you look at it on the server, you may need to reinstall Joomla.

Keep me posted on what you find. Again, this is something we've never heard of and I can't imagine any way that JFBConnect could do this, but we'll gladly help how we can.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
13 years 1 month ago #32842 by severewx
I will take you through the steps that I did.

I logged in to the back end, went to the updates area and clicked find updates. There were 5 available from memory, AcyMailing, HikaShop, JCE Editor, SCLogin and one other that I can't remember.

I started at the top and updated one by one, the first 3 worked fine but once I did SCLogin it generated an error which I regret I didn't take note of what it said. Then when I clicked on the control panel again it came up with an error "Fatal error: Class 'JFBConnectFacebookLibrary' not found in /vhosts/severew/public_html/plugins/system/jfbcsystem/jfbcsystem.php on line 51". This error also appeared when trying to load the homepage.

I went in to the database and disabled the JFBC System Plugin but then it generated another error saying it couldn't find a class for the component J4AGE, disabling that then generated another error for JEvents, disabling that came up with another error for SCLogin. Once those were disabled the site would load but no content would display, only the modules.

That's when I tried to login to the backend and was just given a blank screen, so I loaded index.php in my editor to try and work out why it wasn't working and to my surprise index.php was completely empty.

I have no idea how that happened, especially since as you say there are safe guards in place to prevent access to files such as that.

I have contacted the hosting provider to restore a backup, then I will see if I can replicate the problem.
The topic has been locked.
Support Specialist
13 years 1 month ago #32845 by alzander
Definitely let us know what you find. The chain of events is definitely odd. The "JFBConnectFacebookLibrary" is part of our main component and is loaded from the file /components/com_jfbconnect/libraries/facebook.php. The system plugin simply tries to load that file. Upgrading the SCLogin module doesn't have any affect on the main component or the jfbcsystem plugin, so again, I don't know why that would haven't impacted either of those files.

Additionally, we shouldn't have had any impact on J4AGE or JEvents and especially the index.php file. It's all very curious, and I'm very sorry that we're even implicated in this.

If you find anything more out, please let us know. We'd love to know what happened, and if there's anything in JFBConnect that could do this, we'll obviously get it fixed. Again though, it's not something we've ever heard of, and I can't fathom how it happened.

Good luck,
Alex
The topic has been locked.
  1. Forum
  3. Discontinued Products
  5. JFBConnect Joomla 2.5 Support (CLOSED)
  7. Updating JFBConnect completely destroyed website
From the Blog
Facebook | Twitter | LinkedIn | Blog RSS