This is not coming from Joomla core, but from a 3rd party (likely custom developed) component that exist in your site.
First see if you really need/use this component, or you can simply uninstall it. If you need it, then look for any information you can gather for this component - find the developer and his site/email and ask if there is an update for ...
Well, a quick look inside the templates folder of the site, presented me the ugly truth - it seems that whoever did the upgrade, has never considered to clean up the site from old code/extensions/templates that are incompatible with Joomla 3.
So, in the templates folder I found 8 old templates since Joomla 1.5, that were still considered as installed ...
You'll want to create a custom PHP error handler and have that send you an email.
You can use FILE and FUNCTION and LINE constants to load where the error happened into the email that you alert yourself with.
Take a look at how to do all of that here: https://stackoverflow.com/questions/277224/how-do-i-catch-a-php-fatal-error
I've found out that the easiest/faster method to resolve this was to use a script reading apache's logs and send a mail every day with a summary.
FYI : Server's setup has a daily log rotation, run the script through crontab, just before rotation time.
(Plus : I'm french, so there are french words in the mail being sent).
Here's the script : (I know it ...
I just came across this issue again with another site and remembered what the problem is. This module is that it has changed the way it's loading its helper File/Class and the way the helper.php file is loading the ContentHelperRoute Class, so the ContentHelperRoute isn't anymore available at the default_items.php template file.
require_once __DIR__ ...
I’m answering the question because it is obviously not a Joomla 4 core bug but a mistake in the developer’s coding and the problem would be the same in Joomla 3 too.
If you try to use a Joomla core class in your code you have to include that class on the top of the file otherwise Joomla does not know what it needs to use, so:
It seems your Joomla! instance is corrupted. Since using the Joomla admin does not help with the re-installation, I would suggest Do a complete Joomla! Core manual re-installation / package replacement.
Note: This probably will work better in a local clone of the website on your desktop. Generally avoid doing this on the live website directly.
Create a ...
I recommend you to use this plugin:
it will reintroduce the deprecated DS constant to ease the migration for 2.5.x sites whose extensions still use DS until they get fixed by its developers.
This is one funny problem.
It seems that Joomla includes code from module template overrides in a manner that certain variable names do affect the core JModuleHelper renderModule function.
All you need to do to reproduce this bug-like behavior, is to write the following line in your module template override:
$template = JFactory::getApplication()->...
The screenshot you posted make me think that there must be a Fatal Error somewhere. Enable error_reporting to see if any exists and where it comes from.
Most likely it will be an outdated extension, and by updating or uninstalling/removing it, it will resolve your issue.
Almost every time there is a blank page on a php application, it denotes a php fatal error somewhere. It's not uncommon, it happens and there can be many reasons for it.
First of all, you have to enable Error Reporting, so Joomla/php will print any errors in your browser. This way you will get an idea of what's ...
I recommend running a backup and then upgrading to the latest version of Joomla (currently v3.6.5).
If this does not fix the issue, then try the "Reinstall Joomla core files" option in the Joomla Update component (see below).
If you can't access the back-end you may need to use a manual install method such as the one described at: https://docs.joomla.org/...
We don't have the full information and historical of your site and it's not clear if the update you have is prior to any update attempts. Also, it's not clear if any of your issues existed before your last attempts to update or if there were issues - maybe hidden ones- before than.
What it looks like is that you have ended up with a broken/corrupted/semi-...
Switch to conservative caching, progressive caching should be avoided. You will run into all sorts of issues because of progressive caching, including, but not limited to, memory issues and file system issues. Not to mention, of course, that because of all these constant file writes caused by progressive caching, you may run into hardware failure.
Very few ...
Either, include that helper class on the top of your default.php like:
defined('_JEXEC') or die;
Then you can use that class within your default.php file
Or standardly define your own variable in mod_articles_latest.php like:
$myStuffHere = ArticlesLatestHelper::myCustomFunction($myparam)...
It appears that you don't yet have your file path properly declared.
I'll offer some instructions to correct your tmp path, but you should execute the same technique to eliminate the other Warnings too.
If you have access to your administrator backend:
Go to System > Global Configuration > Server (tab).
The Path to Temp Folder field should read something ...
These are not Errors, these are only Warnings (or is there also any error message connected to these particularly?). This warning usually happens when (due to ie. migration) a file path was changed and the ROOT or BASE path is different than it was before. in Joomla in 'Admin->Global configuration' if you set 'Error Reporting' to 'system default', then these ...
This is a known issue but isn't related to Joomla.
Other people have also ran into the same error, and it's due to SP Page Builder Pro
More information can be found on it here: https://www.joomshaper.com/forums/joomla-3-8
Solution: Update SP Page Builder Pro to 2.5.3
I turned on maximum error reporting and chased the problem down to "Modules Anywhere" component. The upgrade destroyed that component. I couldn't wait for days on the component's message board for an answer, so I restored a backup from 2 weeks ago, then updated the Modules Anywhere component, then updated Joomla.
I tried to visit your site but sucuri says that my country is blocked, so I can't see more about the error.
You can try re-installing Joomla from the admin (Joomla Update component) - or try a manual core re-installation as described here: Class 'JInput' not found after updating to 3.7.3.
You also need to make sure all your installed extensions are ...
I have changed:
This is a known bug and an official solution should be given in the next K2 update.
It seems that there is another place that you have the class "JEditor" defined.
If you have shell (ssh) access to your server, try running the below under your Joomla directory:
grep -R --include=*.php "class JEditor"
You should only see one file (which is the /libraries/cms/editor/editor.php file). If you see 2 files then your problem is with the second ...
It is strange that it return "Notice: Array to string conversion". It usually means that you try to get array variable using string functions. Check what data do you push directly in $_REQUEST.
Back to question. You can always use RAW type of filter if filtering is to strict.
If you still need to override this class please check this plugin sample:
For anyone that might end up here through a Google search, trying to find a solution to a similar problem:
Usually fatal errors especially after an update may mean that some files didn't copied over correctly. Reinstalling Joomla and extensions and update to latest version usually solves such issues.
In many cases I would recommend to perform a manual re-...
If you're in case of a failed upgrade you can check out this tutorial to manual upgrade a Joomla Installation.
It sometimes helps to get out of failed upgrade or at least bring access back to your administrator interface.
This method has been referenced by the community when having trouble ...
Since you have an Akeeba backup, I would use their Akeeba Kickstart offering to restore the server.
Akeeba Kickstart is a downloadable ZIP file which when uploaded to the server along with the JPA backup file, can be accessed via the web to do a stand alone restore.
The application will restore the full database and website file structure. I recommend ...
Looks like the variable $params isn't getting set.
Could be several reasons this is happening, among them that there isn't a menu item set in the current URL.
As @lodder noted, this is old code. The mechanism involving the static call of getMenu from the site application was deprecated years ago; nobody should be using it anymore. (Don't remember precisely ...
Whenever you need any file to be included in the current page then remember,
require() includes file that previously been included.
require_once() ignore the file if it is previously been included in the same page.
try to figure out difference between include(), ...