I'm into Stylish things that just look good and function well.
Gantry issues after upgrade ?
Posted 11 years 9 months ago
Have problems with one staging site since upgrade
I upgraded remote to 4.1.5 and on certain pages I get the following tailed errors. I dont even get part of a response back from the server..
thats when i try and delete a user from backend
front end i get the jomsocial issue looking at the home of jomsocial - not the reffering path given n the warnings/errors below...
BROKEN LINKS REMOVED
Sorry to post here if it isnt a gantry issue but it happens a while after I upgrade and has rok common in the errors...
I'm into Stylish things that just look good and function well.
Re: Gantry issues after upgrade ?
Posted 11 years 9 months ago
I certainly dont know why gantry stuff is loaded for the backend. Also have tried dissabling the rockettheme ximenia template and the errors still happen.
the code not getting the right file is
public function loadClass($class)
{
if ($this->hasBeenChecked($class)) return false;
if (false === $file = apc_fetch($this->prefix . $class)) {
apc_store($this->prefix . $class, $file = $this->findFileForClass($class));
}
if ($file !== false) {
require $file;
return true;
}
$this->addChecked($class);
return false;
}
I'm into Stylish things that just look good and function well.
Re: Gantry issues after upgrade ?
Posted 11 years 9 months ago
This appears to have regressed again upgrading gantry to 4.1.7
I would appreciate a rockettheme engineer to at least help shed some light on to a possible cause so that I might be able to think on and solve it for my environment.
So disable those components and see if this fixes it. But I might agree it is related to APC - still we cant always clear the cache..and its a nasty error.
I dont see removing roksproket and such as a fix as they are very useful utility modules for our site. We are in a position to not upgrade the live site as it stands.
I'm into Stylish things that just look good and function well.
Re: Gantry issues after upgrade ?
Posted 11 years 8 months ago
This is the thread over at jomsocial - but if the error isnt with the standard template you can forgive them not wanting to take a deeper interest. Not saying that it is RT but a combination of something.
require is identical to include except upon failure it will also produce a fatal E_COMPILE_ERROR level error. In other words, it will halt the script whereas include only emits a warning (E_WARNING) which allows the script to continue.
File to change :
/libraries/rokcommon/RokCommon/ClassLoader/ApcLoader.php
Line 37 :
require $file; include $file;