Troubleshooting

Algolia and Undefined index: store_id

Today I have setup the Algolia Queue Runner ( algolia_queue_runner ) which was working fine for all projects I have worked with before. However, today it was different. The Algolia Queue Runner didn’t work at all. Here is what happened every time when the cronjob was running.

$ php /var/www/src/bin/magento indexer:reindex algolia_queue_runner
Algolia Search Queue Runner indexer process unknown error:
Notice: Undefined index: store_id in /var/www/src/vendor/algolia/algoliasearch-magento-2/Model/Queue.php on line 163

$ php /var/www/src/bin/magento indexer:reindex algolia_queue_runner

Algolia Search Queue Runner indexer process unknown error:

Notice: Undefined index: store_id in /var/www/src/vendor/algolia/algoliasearch-magento-2/Model/Queue.php on line 163

The problem was, one of the store views in Stores > Settings > All Stores was disabled for some reason. After enabling the store view, the problem was fixed.

$ php /var/www/src/bin/magento indexer:reindex algolia_queue_runner
Algolia Search Queue Runner index has been rebuilt successfully in 00:00:00

1 2	$ php /var/www/src/bin/magento indexer:reindex algolia_queue_runner Algolia Search Queue Runner index has been rebuilt successfully in 00:00:00

AWS RDS – You Need (at least one of) The SUPER Privilege(s)

Today I had the opportunity to move a local Magento database to an Amazon RDS. Based on the well-documented article Creating a DB Instance Running the MySQL Database Engine I was optimistic to finish the migration pretty soon. But as you know, there is always something that goes wrong.

After creating the database instance class ( db.m3.large ) I have decided to proceed with some test imports before I change any database credentials in Magento.

$ mysql -h customer.1xcpdspit6hz.ap-southeast-2.rds.amazonaws.com -u customer -p
$ source ~/project_20161014_1135.sql

1 2	$ mysql -h customer.1xcpdspit6hz.ap-southeast-2.rds.amazonaws.com -u customer -p $ source ~/project_20161014_1135.sql

Good decision because the first import didn’t run through.

ERROR 1419 (HY000): You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)
Query OK, 0 rows affected (0.01 sec)

1 2	ERROR 1419 (HY000): You do not have the SUPER privilege and binary logging is enabled (you might want to use the less safe log_bin_trust_function_creators variable) Query OK, 0 rows affected (0.01 sec)

I was able to fix the problem by adding the missing parameter log_bin_trust_function_creators as explained here. Before the next import I had to delete the database and create a new one.

ERROR 1227 (42000): Access denied; you need (at least one of) the SUPER privilege(s) for this operation
Query OK, 0 rows affected (0.00 sec)

1 2	ERROR 1227 (42000): Access denied; you need (at least one of) the SUPER privilege(s) for this operation Query OK, 0 rows affected (0.00 sec)

Unfortunately there was another problem with a DEFINER which tried to create a trigger as a different user. On Amazon RDS only a user with SUPER privileges can do that. Therefore, I had to remove the DEFINER from the MySQL schema you see below.

$ sed -i 's/DEFINER=[^*]*\*/\*/g' project_20161014_1135_toimport.sql

1	$ sed -i 's/DEFINER=[^]\/\/g' project_20161014_1135_toimport.sql

That’s it. Now I was able to import my DB on Amazon RDS without errors.

Template “layouts/.html.twig” is not defined in “default.html.twig” at line 12.

I am using the statement include for dynamic sections in MODx.

{% for page in pages.children.visible %}

    {% set color = page.header.color %}
    {% set classes = page.header.body_classes %}

    <section id="{{ classes }}" class="{{ color }}">
        {% include 'layouts/' ~ classes ~ '.html.twig' %}
    </section>

{% endfor %}

{% for page in pages.children.visible %}

{% set color = page.header.color %}

{% set classes = page.header.body_classes %}

{% include 'layouts/' ~ classes ~ '.html.twig' %}

</section>

{% endfor %}

It was working fine so far, but today I received the following exception that basically means, my snippet tried to include a file that doesn’t exist. The variable classes was empty that causes a broken website.

RuntimeException (400) Template "layouts/.html.twig" is not defined in "default.html.twig" at line 12.

1	RuntimeException (400) Template "layouts/.html.twig" is not defined in "default.html.twig" at line 12.

In my case I improved my snippet with an if condition.

{% if classes is not empty %}

    <section id="{{ classes }}" class="{{ color }}">
        {% include 'layouts/' ~ classes ~ '.html.twig' %}
    </section>

{% endif %}

{% if classes is not empty %}

{% include 'layouts/' ~ classes ~ '.html.twig' %}

</section>

{% endif %}