• Solved
  • Update to 6.19 totally broke our site

Hi,

I just ran the recent update and it totally broke our site with error 500 front and back end. WTF. Hugely embarrassing. I got the site back by changing the name of the acy component folder then tries to install the old version and now everything in acymailing is messed up.

I have rarely had problems with updates so why now?

Please tell me how to fix this.

Mel

Same here...if you look at your logs, there is an error being generated:
Fatal error: Cannot declare class Joomla\CMS\Mail\Mail, because the name is already in use in /xxx/public_html/components/com_acymailing/inc/joomlanotification/jMail_J38.php on line 5

This is probably because we have both the old and new versions of AcyMailing installed? At least I do.

I'm not sure, but because that is my situation, and we are still using Acy 5 for now, I had to rename the components/com_acym (the new version's location) to get my site back.

by me

Warning: Table 'd02f281e.#__acym_mail_override' doesn't exist
So I think the database not write the new table for the new "mail override" feature.
I fix it, by import the table from another installation on my database.
The Install is running.

Now I have a new problem: When I get to the users in Acym Administration, is the an Error
1054 Unknown column 'l.type' in 'where clause'
What can I do.

My site also. I sent an email to support (this is not intended to be a duplicate request). I was able to get back "running" by renaming the following subdirectories
/administrator/components/com_acym
/components/com_acym
I just added a 1 to the end. Then I uninstalled acymailing and reinstalled to previous version that I had a copy of (6.12)
Seems to work expect the plugins. I get a message that I need the latest version to get plugins. I tried the latest version again, the site crashes, and I ended up redoing the steps noted here.

@MelanieB , @stratacorps , If you have a valid Essential or Enterprise subscription please raise a support ticket for this (https://www.acymailing.com/support/) and include login credentials for your backend, so we can have a look at it.

@Sputnik41182 Please go to Acymailing->Configuration->Security and run a database integrity check and see if it resolves your issue. You'll find it at the bottom of the page. If it doesn't sole youyr issue and you have a valid Essential or Enterprise subscription you can raise a support ticket for it.

    • DaxSupport Talent

    • Edited

    Hello,

    This is a missing security in the v5, you can choose one of these three solutions:

    • disable the v5 system plugin "Override Joomla mailing system" (element is "acymailingclassmail")
    • uninstall AcyMailing 5 and its plugins if you don't use it anymore
    • update AcyMailing 5 to its latest version

    If the backend isn't accessible, you can disable the v5 plugin from your database in the table xxx_extensions like this:
    https://ibb.co/dDRwKXt

      Dax Thank you so much! Installing the v5 updated (17) fixed the issue. We haven't migrated fully from v5 as of yet because we haven't found a way to handle our distribution lists that aren't supported in v6. Thanks!!

      Thanks for the suggestions (I have both versions too as need some of the functionality in v5 (easysocial etc.).

      I followed the instruction from DAX. I installed latest version of 5, then I did the database integrity check and it fixed some tables, then I installed the latest version 6 again and it is working - no site crash this time. It did display this error after installing but guess it isn't an issue?

      Error
      Duplicate column name 'unsubscribe_total'
      Duplicate column name 'unsubscribe'
      Duplicate column name 'device'
      Duplicate column name 'opened_with'
      Duplicate column name 'mail_settings'

      Sorry for my original post as was a bit stressed when it happened.

      Mel

        MelanieB

        That shouldn't be an issue. For safety you can run a databse integrity check in your v6 as well.

        jvstratum @Sputnik41182 Please go to Acymailing->Configuration->Security and run a database integrity check and see if it resolves your issue. You'll find it at the bottom of the page. If it doesn't sole youyr issue and you have a valid Essential or Enterprise subscription you can raise a support ticket for it.

        Big Thanks, it works.