- Priority: 0
- Status: Waiting on customer
- Theme: Alysum
-
Assigned To:
Fred
- Private: No
- Open Date: 07.05.26, 14:15
- Opened by: Alhemitzar Studio
Ticket #26501 - Creative Elements (CE) cannot be used properly on product pages — multiple conflicts
Creative Elements has multiple issues when used on product pages.
SYMPTOM 1 - CE shows “hook not found” error on unsaved products:
When opening CE on a new product that has not been saved yet, CE returns the error: “Sorry, the content area was not found in your page. You must insert the selected module position (hook) in the current template.”
SYMPTOM 2 - CE is blocked when other product fields contain data:
CE only works if the product is saved with ONLY the product name filled in. If any other field contains data (price, SEO fields, etc.) before opening CE, CE becomes blocked and unusable. The only workaround is to delete all field data, open CE first, then re-enter all other product data afterward.
SYMPTOM 3 - CE button appears on Short Description (Summary) but does not work:
The “Edit with Creative Elements” button is displayed on both the Short Description and Long Description fields, but CE only actually works on the Long Description. Clicking CE on Short Description results in the hook error from Symptom 1.
SYMPTOM 4 - Short Description content destroys CE layout in Long Description:
If CE content has been built in the Long Description field, and any content is then entered in the Short Description via the native PrestaShop editor, the CE-built content in Long Description is converted to plain text -destroying the entire CE layout. This cannot be undone without rebuilding from scratch.
Current workaround:
- Short Description is left empty on all products
- Before every CE editing session: manually clear the Long Description in the native editor → Save → then open CE
Environment:
- PrestaShop: 9.1.0
- Theme: Alysum (Child theme)
- PHP: 8.2
- Store URL: tokatli.chemajka.com
Comments
Hi, Alhemitzar Studio.
Thank you for such a detailed report. We are not the authors of the CE module — we purchased it from WebshopWorks - https://pagebuilder.webshopworks.com, so I can forward these issues directly to the developers.
Hi Fred,
Thank you for the clarification.
I understand that CE is developed by WebshopWorks, however, Creative Elements is one of the key reasons I chose the Alysum theme - it is advertised as a built-in feature and was a deciding factor in my purchase. Since it is part of the theme package, I would appreciate it if you could coordinate with WebshopWorks on my behalf and keep me updated on the resolution.
Thank you.
I completely understand your point.
However, based on my experience, resolving such issues can take quite a long time, if they are resolved at all, especially considering the number of different problems you have reported.
At the same time, I would like to mention that you are the first customer to report issues of this kind during more than 5 years of using the Creative Elements module together with our theme.
If you feel that the current situation does not meet your expectations, I can offer you a refund.
Thank you for the offer, but a refund is not a solution for me. I have invested over a month of work building this store on Alysum, and the deadline for going live is in less than 6 days. Returning the theme at this point is simply not an option.
I also want to be transparent: I use Alysum on another PrestaShop 1.7 store where it works excellently. That is precisely why I chose it again - and why I am concerned. PrestaShop 8 and 9 are the future of the platform, and if Creative Elements cannot function properly on PS 9, this will affect every Alysum customer who upgrades. I may be the first to report it, but I will not be the last.
I would ask you to please escalate these issues directly to WebshopWorks and provide me with a timeline. I am not asking for an immediate fix - I am asking for a commitment that this is being actively addressed.
Alysum is a theme I genuinely like and plan to use on future projects as well. I want this to work - and I am willing to be patient if I know the issue is taken seriously.
Thank you for your patience and for being so open about your situation — I completely understand how critical this is with your go-live deadline just days away.
I want to be transparent: we are not the authors of the Creative Elements module, and the version bundled with Alysum is a separate build from WebshopWorks' main Pro release. That's exactly why I offered a refund — fixes like this depend entirely on their willingness to act, and honestly, I'd put the chances of them agreeing at around 1 in 100. Still, I can submit a formal request to them, if you want, referencing all four symptoms you reported.
In parallel, we will investigate what can be done on our side — particularly around Symptom 4, which sounds the most destructive to your workflow.
I'll keep you updated as soon as there's any news.
Hi Fred,
Thank you for your transparency and for handling my case with such professionalism.
I have been in contact with WebshopWorks regarding the Creative Elements issues, and they confirmed that the conflicts I am experiencing are specific to Alysum's heavily modified version of CE - not present in their official Professional release. They also noted that Alysum is officially compatible only up to CE v2.5.11, which means a resolution would require Alysum to update their own CE integration.
With that in mind, I would like to ask: is there a plan on your side to update the CE integration in Alysum in the near future?
If not, given my very tight deadline, I would need to consider the refund option you offered and find an alternative solution for this project.
I genuinely hope these challenges will be resolved in the coming period - I have been impressed by your honesty and I would look forward to working with Alysum again on future projects.
Thank you for everything.
Let’s try the following approach: please define the most critical issues you currently have and let me know how much time you are willing to wait for a fix. We will then try to provide a solution.
If we are unable to resolve the problems within a reasonable time, we can proceed with a refund.
Hi Fred,
Thank you for the constructive approach. The most critical issue for me is the conflict between Creative Elements and the native PrestaShop editor on product pages - specifically, entering any content in the Short Description field breaks the CE-built Long Description content, making it impossible to use both fields simultaneously.
I am willing to wait up to 2 weeks for a fix. In the meantime, I will have to launch the store in beta mode and hope for the best.
Looking forward to your update.
As I can see in the Pro version, there is no option to edit Summary with CE. I assume that's related to the issue you have. So is it ok for you if we will try to make it works in the same way, I mean just disable CE editor for Summary?
Hi Fred,
Yes, that would work perfectly for me. Disabling CE for the Summary field is exactly what I need.
However, I want to confirm one thing before you proceed - will this change preserve CE functionality in the Long Description field? My priority is to keep CE fully functional there, while using the native editor for Summary only.
Please confirm and feel free to go ahead.
Yes, like you said, we will keep CE Editor for the ling description and try to disable it for summary. That's like it works in the Pro version
I have applied a fix to your store
Hi Fred,
I have migrated the store to the main domain tokatli.rs today. The fix you applied is no longer working - I am getting a template rendering error when trying to open any product. Could you please reapply the fix on the new domain? The store URL is now https://tokatli.rs. All server access credentials remain the same as previously provided in my profile
Here is fixed file.
Upload it to the
Attachments:
Hi Fred,
I have uploaded the admin.js file to /modules/creativeelements/views/js/ and cleared the cache, but the issue persists. I am still unable to open any product for editing. Please see the attached screenshot.
Attachments:
Yes, I see. That's because if the Extended Product module issue, which we did not fixed yet
Hi Fred, good progress!
After deactivating the Extended Product module I can now access products.
The fix partially works - I can add Short Description and it appears correctly on the front-end. However, after saving the Short Description, I can no longer open CE to edit the Long Description. I get the 'content area not found' error again. So the conflict between Short Description and CE is still present when editing an existing product.
Attachments:
We are working on that
Are the FTP credentials correct? Because I do not see any changes when I modify module files
Hi Fred,
I just checked the credentials and noticed that domain was not right, I don't understand why the system didn't save last settings, after migration.
Website URL and URL for the FTP is tokatli.rs
I've updated this info now, but just in case I am writing it here.
user name and password are correct.
I can't reproduce the issue. I have added text to the short description and I still able to edit long description → https://mega.nz/file/9EYkyRhZ#pCy56cZxWjD5GjAeBBiMuG49G6-6dlCUkN1okbBr-yU
Hi Fred,
This works now.
Thank you so much! I am really happy that you found solution and that the website is now working properly.
Thank you!
You are welcome!