TOPIC: Upgrade to 5.2

Hi, I just upgraded to 5.2 and I get the following error when I try to click on an event:

Error: 1146 - Table 'sitesupp_sqms.joom_compojoom_customfields' doesn't exist SQL=SELECT *
FROM joom_compojoom_customfields as f
WHERE `f`.`show`='all' AND `f`.`enabled` = '1' AND `f`.`component` = 'com_matukio.event_title'

Same error when I try to add a custom field in the Matukio backend:
1146 Table 'sitesupp_sqms.joom_compojoom_customfields' doesn't exist SQL=SHOW FULL COLUMNS FROM `joom_compojoom_customfields`

The calendar view shows all the events, but the event list only shows one. I have around 37 events total.

How do I resolve?

I also noticed this on the event list page with the DB error:

<button class="btn btn-default mat_marker_icon" gmaploc="<br />
<b>Catchable fatal error</b>: Object of class stdClass could not be converted to string in <b>/home/sitesupp/public_html/templates/ts_dotcom/html/com_matukio/eventlist/bootstrap3.php</b> on line <b>359</b><br />

Hi,

I had also a problem and found, that after update my categories are gone. Perhaps you have the same thing, just look, if your categories are still there.

Mapache

Hi Brad,

please visit the Matukio dashboard. Seems like the library custom field tables have not been created during the update. Did you update to 5.2.0 or 5.2.1?

Cheers,

Yves

I upgraded to 5.2.1
I can see that the table is NOT in DB and clearly this is the problem (or at least one of them).
How do we resolve this?

Hi Mapache - My categories are all there. I'm thinking that the second error is related to the missing table (or at least I hope that is the only issue).

I can see that the table is NOT in DB and clearly this is the problem (or at least one of them).

Just visit the Matukio dashboard in your backend, there the sql for the custom fields is executed.

Kind regards,

Yves

Ok, yes this fixed the database table issue. I also discovered that the other error I was having in bold red above in this thread was due to an override I had in place for the eventlist. For whatever reason it worked fine in 5.1.3, but caused a problem in 5.2.1. I removed the override and the issue was gone. Thanks!