configuration

• 2021 Nov Cassiopeia Template

• 500 Internal Error when saving an article - reloaded

  After solving couple of times the "500 Internal Server Error" problem as described in a previous post, I received another complaint from one of my clients I host:

  "I also cannot save the articles and here is the error I got
  500 - An error has occurred!"

  Easy cake - I was thinking, but after checking his account, discovered, that all settings described on that article (namely the collation settings in database) where correct.

• Accessing the administration panel

  Okay, you've installed your Joomla site, and want to began to master it. You click on the administrator link in the frontend and instantly hit the wall: a blank page is showing up. What's the deal? The cause is generally simple: This is happening almost always because your 'live-site' setting in your configuration.php file doesn't correspond with your Administration URL. You either have a www in your live-site setting in your configuration.php file and you are accessing your administration backend without the www or vice versa. It's highly recommended to correct this, the problem can impact even your site's Google rating.

• Add article title to Read More links

  the competition for SERP's (Search Engine Ranking Positions) is fierce. The slightest advantage you can gain can make the difference. Good navigation is key here - and part of this is to give some extra info to your visitors of what they will see if they clicking on a given link. Adding the article title to your Read More links is a way to make this happen.

• Adding a new Joomla Super Administrator via phpMyAdmin

  Sometimes the Joomla site owners get a bit paranoic after a time, due to lot of hype about site security. Basically is nothing wrong with, a good site security is based on keeping your accounts secure. But what about when you are hired to do something in a Joomla site and you got ALL access (including FTP and database access) but you discover, that the Joomla account you received is only an Administrator. You can do a lot as an Administrator - but often not enough! Don't tell me, that this never happened to you - unless you are a Joomla rookie. What you can do?

• Blank page when accessing Joom!Fish

  It's weird and scary - in a perfectly functioning Joomla site I installed one of my favourite components, Joom!Fish - remember, I'm the multilang guy - and all I got was a blank screen. Obviously, something gone south... but what?

• Can't log in with admin, no error messages

  This error comes back time-to-time, especially after a Joomla site is moved from one server to another. The symptoms are simple - but frightening. You try to login to the administrator interface as usual, with your well known credentials, and the login box is reloading whitouth any kind of error message and withouth letting you in. No errors in browser console, no error in the logs, and no errors even if you turn the error reporting to maximum or the Joomla debug on. You can try even the tricks described elsewhere in this site to change your admin password - that won't help.

  Why? Because the cause(s) - yeah, there can be multiple causes - are different from having bad credentials! Let's see what you can do about!

  ATTENTION: these tricks are qualified as core hacks, so be careful: backup, wear your lucky hat, keep your finger crossed - and take any other security measures before you proceed - you can ruin your site easily with a wrong move.

• Can't login after moving to new server

  If you search on Google for the term "joomla can't login after moving to new server" - or something similar, you will get more, than 1 million hits for most of the combinations.

  So, you aren't alone. And there are plenty of suggestions, on what might gone wrong and how you might find that, and there are verious fixes. But what if you moved the site to another domain? From development server to it's final place? This is a subject wich is rarely touched by those advices.

• Cannot modify header information - headers already sent

  This warning message is produced by PHP if a program attempts to send an additional HTTP header after the separator (and hence all the headers) has already been sent. In the HTTP protocol a server response consists of a group of headers followed by a body, separated by a single blank line (i.e. a line containing only a carriage-return).

• Change the default Joomla database prefix

  Every hacker in this world knows, that by default all Joomla database tables have the "jos_" prefix. Is that well known, than even automated defacing scripts are using this, and there are a lot of "tools" which are capable to automatically probing your site having this presumption built into them.