Update:
I looked for the string "custom" within the DATABASE of the website that gives me that error page, and I found that the _modules table has the string "custom" as a value in the "module" column of some of the rows, not all
All the other rows have the "mod_custom" string as a value or some other "mod_*" value.
I changed the value "custom" string to "mod_custom" and now the home page is visible again.
So the question how was it possible for this to happen? This apparently happened either during the update from J4 to J5 or right after. And more importantly how to prevent this from happening again!!!
Has anyone ever experienced a similar thing?
I looked for the string "custom" within the DATABASE of the website that gives me that error page, and I found that the _modules table has the string "custom" as a value in the "module" column of some of the rows, not all
All the other rows have the "mod_custom" string as a value or some other "mod_*" value.
I changed the value "custom" string to "mod_custom" and now the home page is visible again.
So the question how was it possible for this to happen? This apparently happened either during the update from J4 to J5 or right after. And more importantly how to prevent this from happening again!!!
Has anyone ever experienced a similar thing?
Statistics: Posted by antonios — Wed Dec 11, 2024 11:19 pm