What killed Joomla

  • Hello.

    Today I performed a long overdue update from Joomla 3.8.6 to 3.8.11.

    When I try to log in to the site, I get the following error messages:

    JAuthentication:: authenticate: Error loading the plugin: plgauthenticationjoomla

    JAuthentication:: authenticate: Error loading the plugin: plgauthenticationcookie

    I was able to neutralize those with the cookies because I was / am still logged in to the backend. So I deactivated the cookie authentication plugin. If I also deactivate the Joomla authentication plug-in, the following message comes as a little surprise:

    JAuthentication:: __ construct: The authentication libraries could not be loaded!

    Apparently all plugins no longer work / no longer work properly, because if I want to create a post or install an extension, for example, this does not work either.

    The following is displayed under "Extensions / Check":

    JFolder:: folder: The path is not a directory! Path: /var/www/virtual/web41615.pfweb.eu/DOMAIN/ htdocs / plugins

    I currently don't have access to the directory path above because I am running the site with a friend. I am just about to get the access data.

    As I wrote above, I am currently still logged in to the backend, but I don't know how long this will last.

    I hope I can be helped quickly!

  • Oh, by the way, I'm with i-MSCP and when I try the file path

    /var/www/virtual/web41615.pfweb.eu/DOMAIN/htdocs/plugins

    to browse comes "Error 404 Page not found", but in an i-MSCP layout.

  • Ok, now I'm out of the backend and can no longer log in.

  • So I deactivated the cookie authentication plugin

    1. Mortal sin

    If I also deactivate the Joomla authentication plugin

    2. Mortal sin

    Activate both plugins again. If necessary via database.

    Delete browser caches, Joomla caches (folder / cache / and / administrator / cache / via FTP or whatever you use there, empty except for the index.html file)

    Delete browser cookies.

    Empty (do not delete) in the database table #__sessions.

    Copy an unzipped FULL-Package 3.8.11 without folder / installation / via FTP over it. Or whatever you use there.

    Go to Extensions> Database and click the Repair button.

    Set report errors to maximum in the configuration or directly in the configuration.php

    And if the front end still does not work and the back end works, you should by no means deactivate Joomla features, but rather look for front end errors: template, special registration form?, Outdated template framework etc. pp.

  • I'm sorry that I have to ask that bumblingly now. But how exactly do I get into the database?

    I use FileZilla, an FTP client.

    In my cache folder there is only one file called index.html. When I open this, only a blank page opens in the browser. This is also the case in administrator / cache.

    I don't have a / installation / folder.

    The backend was by no means still active, I was just logged in.

    PS: Even before I was kicked out of the backend, the Joomla authentication plugin was reactivated.

    Thank you so far

  • how exactly do I get into the database?

    Unfortunately I have no idea where it is with "i-MSCP" and how your shared hosting is structured and whether the panel has any graphical interface that you might get on with ....

    Are you able. edit one of your php files? For a "nasty rush" code that I would then tinker with.

    If otherwise empty, everything is fine.

    I don't have a / installation / folder.

    You just have to read carefully

    Copy an unpacked FULL package 3.8.11 without the / installation / folder over it via FTP.

    Get the FULL package here.

    Unzip it.

    Delete the folder / installation /.

    To be on the safe side with you probably also / templates /.

    Then copy the rest into your web space = iron over it.

    Then we are sure that all relevant files are actually available.

    Now comes the crux of the matter before you do that. Does your website run as fast-cgi, fcgi or something similar?

    The easiest way to find out is to go to the backend

    A note would also be that there were no problems with the initial installation after you uploaded the Joomla files via FTP, if you did a standard installation at that time.

    Pooh, written everything complicated ...

  • So first of all, thank you very much for this flood of data.

    Are you able. edit one of your php files?

    I can drag it to my computer via FTP, edit it and then insert it again. So yes.

    Unfortunately I have no idea where it is with "i-MSCP" and how your shared hosting is structured and whether the panel has any graphical interface that you might get on with ....

    So far, unfortunately, neither have I, since, as I said, I don't have the access data. A friend has her. ↓

    A note would also be that there were no problems with the initial installation after you uploaded the Joomla files via FTP, if you did a standard installation at that time.

    The thing is, I didn't do the initial installation, but said friend with whom I run the site. I made an appointment with him for today to clarify everything.

    Then copy the rest into your web space = iron over it.

    The question that will probably finally make me a technical analyst: I just copy the folder into my FTP without any sub-folders or anything else. Just go in, right?

    Thanks for your help and patience!

  • That would be the code if you want to try to reactivate the plugin without database access:

    1.) A copy of the file

    /administrator/templates/isis/login.php

    create so that you can restore the original in an emergency.

    2.) In the file

    /administrator/templates/isis/login.php

    which you open with a suitable text editor,

    search this line (line 10 or so)

    3.) BEHIND this line insert a blank line and then the following code

    Show all

    4.) Go to the backend login page. Remains white, with the text "DONE: Now remove the code again!"

    5.) Remove the above code again. Try a login.

    If you see a token or session error text, delete cookies in the browser or use a different one.

    And go to the login page again.

  • And one more short objection:

    When I just tried to log in again, instead of the error message above, I got something like: "The security token is incorrect. Please refresh the page and try again."

    After updating, the old error message came back and I cannot replicate the other case.

  • It should be said that I have not yet followed the steps.

  • Ok code was introduced and taken out again. All plugins are active again and I get (again) this message:

    JAuthentication:: authenticate: Error loading the plugin: plgauthenticationjoomla

    JAuthentication:: authenticate: Error loading the plugin: plgauthenticationcookie

    Now I'll try the FULL package.

  • I just copy the folder into my FTP without any sub-folders or anything else. Just go in, right?

    All folders and files that you see after unzipping, maybe also in a subfolder of the unzipped result.

    These are the crucial folders. So you can copy over individually.

    /Administrator/

    / components /

    / includes /

    / language /

    / layouts /

    / libraries /

    / media /

    / modules /

    and keep all files in the root directory.

    When FileZilla says "Overwrite?" asks a yes to everyone.

    As I said, in case you come back to the backend anyway,

    Instead of ironing it over, you can go to Extensions> Database and try the repair button.

    And / or previously Components> Joomla Update> Upload and Update:

    And there the FULL package, the zipped onethat you have downloaded, "install" again and then to be sure

    Go to Extensions> Database and try the Repair button.

    Since we don't know whether the Joomla update was fundamentally complete.

    And then repair the front end afterwards.

    As a note: Normally extensions with an ID less than 10,000 belong to the Joomla core. So you should deactivate it with care. Or before you deactivate it, take a look at the plugin. It says that you shouldn't deactivate this if ...

  • All plugins are active again and I get this message (again)

    Since this is only in the front end, I initially assume that the installed stuff is to blame. Because both plugins work in the backend.

    The "ironing over" is not wrong at first.

    Just get in touch again. Maybe you can get a more detailed error message. Who is to blame.

  • When FileZilla says "Overwrite?" asks a yes to everyone.

    Am I correct in assuming that all my contributions will then be gone? Or are these the folders that I deleted before (in the new file) and are therefore not overwritten?

    Because both plugins work in the backend.

    I get the same error message in the front and back end.