Support » Plugin: Organize Series » Upper/Lower Case problem in SQL

  • Resolved José Luís


    Great plugin, thanks!

    I think I’ve detected a little glitch on the last few days (using version 2.4.6), though…

    Series’ icons disappeared and I noticed some strange entries on my error_log:

    Erro de banco de dados do WordPress Table 'xxx_wordpress.wp_orgseriesicons' doesn't exist para a consulta SELECT icon FROM wp_orgseriesicons WHERE term_id=343 feita por require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/xxx/sidebar-page.php'), get_template_part, locate_template, load_template, require('/themes/xxx/content-page.php'), the_content, apply_filters('the_content'), call_user_func_array, do_shortcode, preg_replace_callback, do_shortcode_tag, call_user_func, jlcarneiro_series_list_shortcode, wp_serieslist_display_code, token_replace, get_series_icon, series_get_icons

    I suspected of the upper/lower case on the table’s name. Tested the SQL Query on phpMyAdmin and it failed. Then I edited orgSeries-icon.php changing all ocurrences of “orgseriesicons” to “orgSeriesIcons” and it started working again.

    Can you check it, please?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi Jose, actually there was some code in Organize Series 2.4.6 that was supposed to migrate series data from a table named orgSeriesIcons, to a table with the same name but all in lowercase. The reason for this is because it is generally a “bad idea” to have camelCase table names and the name of this table is a hallmark for the origins of the table way back when Organize Series was first created by an inexperienced developer at the time (ahem, me).

    Anyways, your fix will temporarily make things work but the better fix would be to export your info from the existing table, delete it, then create a new table named orgseriesicons and import your data back into it.

    Sorry about the problem.

    I’m having the same errors…

    is it not just possible to rename the table?

    That’s what I did while I waited for an official solution.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Upper/Lower Case problem in SQL’ is closed to new replies.