Promokit Helpdesk Alysum

Hi,

Thank you for your reply.

We have already tested the possibilities you mentioned and can rule out our Custom CSS as the cause.

The issue has been reproduced:

- With our Custom CSS completely disabled.
- With CSS combination/minification disabled.
- After clearing the PrestaShop cache and regenerating Creative Elements assets.
- Before the additional third-party modules currently installed in the shop were added.
- On a different temporary server, where we performed the same tests and obtained the same intermittent behaviour.

Therefore, the issue does not appear to be specific to the current hosting environment either.

The behaviour is intermittent: the homepage can render correctly and later lose some styles without any changes being made.

We have also compared the working and faulty states. This does not appear to be a CSS syntax error causing the stylesheet to stop being parsed. Instead, complete CSS blocks required by Alysum/Promokit modules are sometimes loaded and sometimes missing.

For example, we have observed the styles for a Creative Elements template (".elementor-3010000") disappear, as well as generic styles required by "pklookbook" (".lookbook-item", ".lookbook-products-list", ".lookbook-image", ".pois", etc.).

When these styles are present, the homepage renders correctly. When they are missing, the affected elements lose their layout.

This suggests that there may be an issue with the way Alysum, Creative Elements and the Promokit modules register/load their assets, possibly related to the module or hook execution order, rather than an invalid Custom CSS file.

As a temporary workaround, we have copied the CSS rules that intermittently fail to load into Custom CSS. Therefore, these rules may sometimes be duplicated, but this prevents the live shop from appearing broken when the original module styles are missing.

At this point, we would appreciate it if you could investigate the issue directly on the installation and determine why these module styles are intermittently not being loaded.

You already have FTP and PrestaShop Back Office access to the shop, so please feel free to use them to debug the theme and module asset loading directly.

Buenos días, como les decía hemos aplicado en los css personalizados del theme una réplica de los css de lookbook para que se vea siempre bien, si lo elimino (adjunto en el css lo que he eliminado ahora) ya no se ve bien la home. Pero puede que cuando se vuelva a generar la caché de PrestaShop sí que se vea, es un error intermitente.
Mirad la home ahora (si podéis) y mi pantallazo para que veáis cómo se ve.

https://doadoa.es/ image.png

Si incluyo de nuevo en theme Settings>Custom CSS lo que hay en el archivo adjunto ya se verá bien, pero lo suyo es que siempre se incluya en el css que se publica en la web. Podéis probar a quitar la compresión CSS en los ajustes de rendimiento, sigue pasando lo mismo.

Good morning, as I mentioned, we've applied a replica of Lookbook's CSS to the theme's custom CSS to ensure it always displays correctly. If you remove it (I've attached the CSS file showing what I've removed), the homepage no longer displays correctly. However, it might work once the PrestaShop cache is regenerated; it's an intermittent issue.
Please take a look at the homepage now (if you can) and my screenshot to see how it looks.

https://doadoa.es/ image.png

If I reinsert the content from the attached file into the theme's Settings > Custom CSS, it will display correctly, but ideally, it should always be included in the CSS that's published on the website. You can try disabling CSS compression in the performance settings, but the problem persists.

OK, you can now log in.

Thank you

Hi,

Were you able to fix it?

Thanks

Hi,

Since you already have access to the back office, could you please also review the Promokit Lookbook module as a whole? We have found several issues with its administration:

When we edit the title of an existing Lookbook and save it, the module displays “Updated successfully”, but the new title is not actually saved/shown.
When we create a new Lookbook, it does not appear in the list in the back office.
There are no related PHP errors in the error_log.
However, when checking the database directly, we can see that several Lookbooks created during our tests have actually been saved there, even though they are not displayed in the back office.

So it seems that the records are being created in the database, but the module is not retrieving or displaying them correctly in the administration area.

Could you please check why the Lookbooks stored in the database are not appearing in the back-office list, and why editing a title returns a successful update message even though the change is not reflected?

We would also like to clarify the intended functionality of the module: is it possible to create and manage several different Lookbooks and then choose which one is displayed on the homepage? If so, could you please check that this functionality is working correctly as well?

Since there seem to be several related issues, we would appreciate it if you could review the module's back-office functionality as a whole rather than only one specific error.

Thank you!

Hello,

Okay. I'll wait.

Thank you.