when I click on "Mappings" on a previously created category, then comes the following erro

[delphin]

Unknown column ‘a.set_link’ in ‘field list’ SQL=SELECT a.id, a.listing_id_fk, a.published, a.set_link, a.ordering, a.field_width, a.sort_by, a.sort_by_direction,b.title, b.custom_title FROM jomkas_advlisting_mappings AS a LEFT JOIN jomkas_advlisting_fields AS b ON b.id = a.field_id_fk WHERE a.listing_id_fk = 100 ORDER BY a.ordering asc

Unknown column ‘a.set_link’ in ‘field list’ SQL=SELECT a.id, a.listing_id_fk, a.published, a.set_link, a.ordering, a.field_width, a.sort_by, a.sort_by_direction,b.title, b.custom_title FROM jomkas_advlisting_mappings AS a LEFT JOIN jomkas_advlisting_fields AS b ON b.id = a.field_id_fk WHERE a.listing_id_fk = 100 ORDER BY a.ordering asc LIMIT 0, 20

Unknown column ‘a.set_link’ in ‘field list’ SQL=SELECT a.id, a.listing_id_fk, a.published, a.set_link, a.ordering, a.field_width, a.sort_by, a.sort_by_direction,b.title, b.custom_title FROM jomkas_advlisting_mappings AS a LEFT JOIN jomkas_advlisting_fields AS b ON b.id = a.field_id_fk WHERE a.listing_id_fk = 100 ORDER BY a.ordering asc

Warning: mysql_num_rows() expects parameter 1 to be resource, boolean given in /www/htdocs/w00fa4d3/gebraucht-waffen-koeln/libraries/joomla/database/database/mysql.php on line 293

Warning: mysql_num_rows() expects parameter 1 to be resource, boolean given in /www/htdocs/w00fa4d3/gebraucht-waffen-koeln/libraries/joomla/database/database/mysql.php on line 293

I need help so that the component is running.

Greetings from Germany

[Michael Gilkes]

@delphin. Thanks for posting. From the error, it seems that your SQL tables are missing a new column, ‘set_link’. This was added in version 1.5. Please let me know how you updated the component. Did you use the Extension Manager? Or did you manually copy and replace the files?

When upgrading, you need to use the Extension Manager to update the component properly. if you need assistance with this, please create a temporary admin login for me, and email me the details, and I will personally look at and fix it for you.

[Michael Gilkes]

@delphin. Ok, I have looked at this issue. What happens, it seems, is that the update SQL was not installed properly for some reason at the first installation/update, and thus certain things are missing.

You can manually fix it by accessing 1.5.0.sql in the backend/sql/updates folder, and copy/paste/execute the SQL statements in that file direction into your phpMyAdmin console. This will fix it manually.

If you want to wait I bit, I am going to release version 1.5.1 some time today to address this issue. So, all you will need to do is to upgrade to the minor release version 1.5.1.

[Author]

Posts