4
In your Joomla installation directory reach templates/themeXXX/error.php file.
Edit the error.php file as shown below, locate this line of code:
If you don't want to change address bar url then you can use below code
if (($this->error->getCode()) == '404') {
header("HTTP/1.0 404 Not Found");
echo file_get_contents(JURI::root().'alias-of-404-article-...
3
I had this issue now a second time on another system and tried to fix it the same way.
I've recognized, that this could be fixed easier:
Setup a new local Sytem of Joomla with the last running Joomla version (which was 3.9.3 in this case)
Exported the database from the live system and imported it to my local Joomla
Repaired all database failures with the ...
3
In libraries/legacy/controller/legacy.php we changed:
throw new Exception(JText::sprintf('JLIB_APPLICATION_ERROR_VIEW_NOT_FOUND', $name, $type, $prefix), 500);
to
throw new Exception(JText::sprintf('JLIB_APPLICATION_ERROR_VIEW_NOT_FOUND', $name, $type, $prefix), 404);
2
Although there is limited information, based on the fact this only occurs during times of heavy site traffic, my thought is you've either exceeded your maximum concurrent connection for the Mysql database or the database crashes do to lack of server resources.
Either way, check your database logs. Update your post with them if you need further help.
2
With the limited info you provided there are only 2 things that are most likely the reason.
your server does not have enough resources and may need an upgrade.
you have a php injected script that is constantly running a script
that uses up the resources.
I would look at your resources, via control panel server side and see if indeed there are constant php ...
2
Some things to try (assuming you can get to some or all of these pages):
update to the latest version of Joomla (if you haven't already)
update third party extensions to the latest versions
switch to the alternative admin template to see if the issue is
template related
check if you have any third party administrator modules installed and
if so, temporarily ...
2
Change
JURI::root().'index.php?/es-co/option=com_content&view=article&id=23'
to
JURI::root().'?option=com_content&view=article&id=23'
Reason:
JURI::root().'index.php?/es-co/option=com_content&view=article&id=23'
is being routed to (try it in your browser):
http://example.com/es-co/?/es-co/option=com_content&view=article&...
2
It sounds like your error page may have the wrong permissions set on it so that it isn't able to show, so you end up with a 500 error instead. 500 errors are almost always caused by two things:
Something wrong in your htaccess file
bad permissions on a file or folder
there are other causes, but in my experience those are the two biggies.
2
Recent Joomla version can handle the errors based on native PHP exceptions, so just throw an exception with corresponding message and value, Joomla will display the error page set (template, custom…)
if ($someCheck)
{
throw new Exception(JText::_('JERROR_LAYOUT_PAGE_NOT_FOUND'), 404);
}
Source: Whats the correct way for exception handling?
1
Green,
That's a very unorthodox method of configuring your site.
Once you have a system generated configuration.php file from the install, you would be best simply moving that around and adjusting it rather than creating one from scratch.
When you say "automatic install" do you mean via a hosting tool like softaculous in cPanel, or do you mean by ...
1
go to /administrator/index.php?option=com_installer&view=database
click on fix
1
I found a solution that worked for me and where I had not to dig into the code and database.
Setup a new local Sytem of Joomla with the last running Joomla version (which was 3.6.1 in my case)
Exported the database from the live system and imported it to my local Joomla
Repaired all database failures with the Joomla autorepair function. On my local system ...
1
You should be able to adjust the error.php file to set the header either with the
Joomla way:
$app = JFactory::getApplication();
$app->setHeader('HTTP/1.1', '404 Not Found',true);
$app->sendHeaders();
PHP way
header('HTTP/1.1 404 Not Found', true, 404);
1
In order to call the 404 error page from your component, simply raise a 404 error using JError. For example:
JError::raiseError(404, JText::_('COM_CONTENT_ERROR_ARTICLE_NOT_FOUND'));
1
I have Resolved this issue this is very basic solution .
1. You must have to give permissions public to all special and register menu.
2:You must have to give permissions public to all special and register content .
After This .warning error Resolved
1
If you want to use HTML (such as to display an image with a link) then you need to display it in a page that is outputting HTML.
It's possible in CSS/HTML to make an image take up the whole screen - linking directly to an image isn't the best way to achieve that effect.
You could either write a small, static page outside-of-Joomla and redirect to that ...
1
Although not using proper terminology, I think I got what your main problem is.
First of all, what you have now is not a right way to deal with non-found pages/urls (404 errors). Actually you don't return a 404 status error, instead you return a 200 status page with content. So it looks like any faulty url leads to somewhere in your site.
Then you don't ...
1
You should not worry about admin 404 page. None of the front-end users should have access to that section. But if you really want to check it first of all upload a fresh system files to make sure that none of them are broken. Make sure system is up-to-date. If nothing changes that means that one of the extensions you have installed is breaking default system ...
1
Sounds like your problem is too many SQL connections, combined with CPU overload. Here's what I did for a site that gets 25,000 hits a day that I host:
If you have a dedicated or VPS, increase number of SQL connections to 150. Most servers have them set to 100. Contact your host support and have them go through your Tweak Settings in WHM. If you need good ...
1
Shared hosting is very bad for any serious business. Before doing anything, you should invest a bit more money into your website and move to a VPS (that move will pay for itself since Google ranks faster websites higher).
Once you do that, you can then tweak your InnoDB settings (and perhaps modify the core) in order to enhance the performance of your ...
1
A lot of traffic can make the Joomla sessions table cause a high Mysql disk I/O. This can result in myslq timing out.
Check the resource monitor for Mysql disk I/O.
It's possible this does not show up in the form of high CPU or RAM usage.
1
I see two ways to do that, but you need access to server in ssh to perform (linux):
/var/log/apache2/error.log is a good start to know more about this error
usually i use and a command line tool like http://xmlsoft.org/xmllint.html
that allows you to check for mal-formed xml files in whole file structure.
This is probably not the direct clue to your ...
1
You should set error_reporting to maximum in configuration.php, then check the line of error.
Set to NONE if don't want the errors to be shown.
1
I fixed it! This is how:
Create a menu item with access registered with the description "ata" and menu item type category blog that links to your "ata" category. This will only be visible to logged in users.
Create a menu item with access guest (not public), with the description "ata" and menu item type login form. Set the login redirect to the URL of ...
1
Have you recently updated to Joomla 3.5x and then the issue started? Have you checked that all your extensions are compatible with Joomla 3.5?
I would suggest to look in your extensions and disable any 3rd party that could look outdated.
Start with the plugins, you may have an old non-compatible content plugin installed for your articles. Not sure if you ...
1
It's just the way the router works. The number is the ID of the article. Joomla needs to know how to convert the URL to a page, and so one way is to look what number is in the URL and see if that matches an article.
Everything beyond the number is for SEO / human readable links, but Joomla doesn't need to know that, so it can be anything.
Your 404 pages ...
1
Those 403 are on pages you are browsing, or for assets like css, js, images files etc?
403 error means, that access is forbidden for the requested file.
Since you moved your site:
Check your htaccess file for any possible required modifications, to match your site's new location.
Those 403 errors, can be on requests for external to your joomla site ...
1
If you're in case of a failed upgrade you can check out this tutorial to manual upgrade a Joomla Installation.
https://gist.github.com/mbabker/d7bfb4e1e2fbc6b7815a733607f89281
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 ...
1
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 ...
Only top voted, non community-wiki answers of a minimum length are eligible