PHP Fatal error: Class 'JFactory' not found

I have faced this issue in Joomla site and searched the forums but none of the forums including joomla did not give solution for me.
They simply suggest to check joomla version, php version compatibility and php extensions.
Finally I have fixed the issue.


Issue:-
---------
 [26-Sep-2014 18:11:29 Europe/Berlin] PHP Fatal error: Class 'JFactory' not found in /home/test/public_html/index.php on line 31

Cause & Solution:-
-----------------------
In my case, it seems file which gives the class JFactory was missed.

/home/test/public_html/libraries/joomla/factory.php --->Core file for Joomla.

Simply restore that file under proper path to fix the issue.

Comments

  1. Unknown5 March 2015 at 05:27

    Hi, thanks for sharing your solution. How do I restore the file path?
    Thanks

    ReplyDelete
    Replies
    1. saravananlinux7 March 2015 at 21:35

      Hello Desarrollo,

      That file [factory.php] is comes under Joomla by default.
      So please download the full Joomla package and simply copy this file to /home/xxx/public_html/libraries/joomla.
      Otherwise if you have any other Joomla sites in your server then simply copy this file to the site which you are facing issue.

      Thank you

      Delete
    2. portcitytechnology26 April 2016 at 15:24

      Thanks for your post, it saved me a bunch of running around. If anyone needs a fresh copy of this file, which I ran across on an old site of mine (customer didn't want to upgrade yet), I found a spot to download the older versions of Joomla, so you can get a fresh copy of factory.php here: http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=6311

      Delete
    3. saravananlinux26 April 2016 at 21:20

      Dave, Thank you.

      Delete

Post a Comment

Popular posts from this blog

KVM & Qemu

QEMU is a powerful emulator, which means that it can emulate a variety of processor types. Xen uses QEMU for HVM guests, more specifically for the HVM guest's device model. The Xen-specific QEMU is called qemu-dm (short for QEMU device model) QEMU uses emulation; KVM uses processor extensions (intel-VT) for virtualization. Both Xen and KVM merge their various functionality to upstream QEMU, that way upstream QEMU can be used directly to accomplish Xen device model emulation, etc. Xen is unique in that it has paravirtualized guests that don't require hardware virtualization. Both Xen and KVM have paravirtualized device drivers that can run on top of the HVM guests. The QEMU hypervisor is very similar to the KVM hypervisor. Both are controlled through libvirt, both support the same feature set, and all virtual machine images that are compatible with KVM are also compatible with QEMU. The main difference is that QEMU does not support native virtualization. Consequently, QEMU has
Read more

docker.errors.APIError: 400 Client Error client is newer than server

You can face this issue when you are trying to use docker python library. Error: docker.errors.APIError: 400 Client Error: Bad Request for url: http+docker://localunixsocket/v1.26/images/json?only_ids=0&all=0 ("client is newer than server (client API version: 1.26, server API version: 1.24)") Solution: client= docker.from_env(version='auto') Use parameter "version" when instantiating a client.
Read more