Home News Contact Us Forum About Us Demos Products F.A.Q.
Shopping Cart
You currently have 0 items in your cart.


Recent Events
  • 31/12/2023 New Year SALE

    We are glad to announce New Year SALE. 25% discount for all our extensions. Use NY24 coupon code. Hurry up the discount is valid till 7 January.

  • 21/11/2023 BLACK FRIDAY 23 is coming

    BIG SALE, 35% discount for all our extensions. Use BF23 coupon code. Hurry up the discount is valid till 27 November.


2Checkout.com, Inc. is an authorized retailer of goods and services provided by ARI Soft. 2CheckOut




Follow us on twitter



Welcome, Guest
Please Login or Register.    Lost Password?

Receiving FATAL ERROR in our production environmen
(1 viewing) (1) Guest
Go to bottomPage: 123
TOPIC: Receiving FATAL ERROR in our production environmen
#64729
Receiving FATAL ERROR in our production environmen 5 Years, 1 Month ago Karma: 0
We are using ARI Smart Content in a University Environment.

We have a 'development' environment where the tool worked perfectly, no problems at all. But when we put it in our production environment (which has more security and different permissions), we get the following error:

Error:
Code:

Fatal error: require_once(): Failed opening required '/mnt/web/cms/genetics/cache/arismartcontent_config.php' (include_path='.:/usr/share/php7:/usr/share/php7/PEAR') in /mnt/web/cms/genetics/administrator/components/com_arismartcontent/kernel/Utils/class.Config.php on line 62



Note this error comes up on our HOME PAGE of the website, so basically the site 'crashes' and is a complete white page, until I turned the error handler on, and i can see the error above.

For our site to not be 'white screen', I had to disable ALL of the plugins with ARI Smart Content.

Also in our production environment, when I go to the ADMINISTRATION page for ARI SMART CONTENT I also get a 500 error.

Any ideas?

thanks.
The administrator has disabled public write access.
 
#64730
Re:Receiving FATAL ERROR in our production environmen 5 Years, 1 Month ago Karma: 747
Hello,

It seems the extension can't save config file to <joomla_directory>/cache folder. Probably doesn't have permissions to do it.

Regards,
ARI Soft
The administrator has disabled public write access.
 
#64731
Re:Receiving FATAL ERROR in our production environmen 5 Years, 1 Month ago Karma: 0
That is what I thought... can you suggest what adjustment I need to make so your extension DOES have the right permissions to the cache folder?

Since we are a university environment our permissions are set very, very tight.

thanks,
Laura
The administrator has disabled public write access.
 
#64732
Re:Receiving FATAL ERROR in our production environmen 5 Years, 1 Month ago Karma: 747
It should have permissions to write to this folder. Another solution is copy this file from your dev env to production.

Regards,
ARI Soft
The administrator has disabled public write access.
 
#64733
Re:Receiving FATAL ERROR in our production environmen 5 Years, 1 Month ago Karma: 0
If I 'put' this file into the cache folder, will it get cleared out when we 'clear cache' and have to be rebuilt?

thanks,
Laura
The administrator has disabled public write access.
 
#64734
Re:Receiving FATAL ERROR in our production environmen 5 Years, 1 Month ago Karma: 747
If you mean "System -> Clear cache" page on Joomla! backend then it should work because Joomla! clear files from sub-folders in "cache" folder.

Regards,
ARI Soft
The administrator has disabled public write access.
 
Go to topPage: 123