Forum Replies Created

Viewing 15 replies - 1 through 15 (of 19 total)
  • Plugin Support BSF – Ravi Gojiya

    (@ravigojiya)

    Hi @itapress,

    We truly appreciate the effort you are putting into testing Spectra’s translations.

    The AI Assistant you are referring to is powered by our Zip AI library, which runs as a shared component across several of our products and currently carries its own text domain for that reason.

    The good news is that the text domain consolidation work you helped surface with your earlier reports is already on our development team’s radar. We have logged this as part of the same track of work, so the AI Assistant strings will be looked at alongside the Setup Wizard and Design Library fixes.

    We will keep you posted as progress is made.

    Have a nice day ahead!

    Plugin Support BSF – Ravi Gojiya

    (@ravigojiya)

    Hi @kins,

    Thank you for taking the time to document this so clearly and share it with the community. This kind of detailed diagnosis genuinely helps.

    You have identified the root cause correctly. When a Spectra Form block is placed inside a template, the post_id sent in the AJAX request points to the currently viewed post rather than the template where the form block is actually defined. The AJAX handler then fails to locate the form configuration and returns the 400 error.

    We were able to reproduce this on our end and have already logged it with our development team for a proper fix in an upcoming release. In the meantime, we appreciate your patience and understanding

    Thanks again for sharing this so thoroughly. It saves a lot of debugging time for others who run into the same situation.

    Have a great day ahead!

    Plugin Support BSF – Ravi Gojiya

    (@ravigojiya)

    Hi @itapress,

    Thank you for pointing this out, and apologies for the inconvenience caused.

    The Design Library is also part of a shared library we use across multiple plugins, which is why it carries a separate text domain. We will pass this along to our development team to explore making it compatible with standard translation workflows.

    We appreciate your feedback.

    Have a wonderful day ahead!

    Plugin Support BSF – Ravi Gojiya

    (@ravigojiya)

    Hi @itapress,

    Thank you for pointing this out, and apologies for the inconvenience caused.

    The Setup Wizard is part of a shared library we use across our plugins, which is why it has its own text domain. We will share this feedback with our development team to look into making it compatible with standard translation workflows.

    We appreciate you taking the time to report this.

    Have a great day ahead!

    Plugin Support BSF – Ravi Gojiya

    (@ravigojiya)

    Hi @itapress,

    Thank you for taking the time to test this and report it.

    You are correct that the Dutch translation is 100% complete on translate.wordpress.org, and we appreciate you verifying that before reporting.

    We looked into this on our end and confirmed the issue. Block names and descriptions shown in the Block inserter and Gutenberg editor are loaded through JavaScript, which relies on a separate set of translation files. There is currently a mismatch between how those files are generated for the language pack and how WordPress expects to load them at runtime. This means the block editor strings remain in English even when the site language is set to Dutch or any other language.

    This is a bug on our end and not something you can fix from your side. We have logged it internally, and the development team is looking into a fix.

    Thank you again for flagging this. We are sorry for the inconvenience.

    Have a great day ahead!

    Plugin Support BSF – Ravi Gojiya

    (@ravigojiya)

    Hi @wwdes,

    Thanks for reaching out and apologies for the inconvenience caused!

    What you are running into is most likely related to how the Twenty Twenty Five theme handles global padding. The theme applies padding at the root level through its theme.json settings, and this affects all blocks, including full width ones, so even a Spectra Container set to full width will appear to have spacing on the sides.

    This is controlled by the theme rather than Spectra itself, but there is a way to address it. You can try going to Appearance > Editor > Styles > Edit Styles and check if there is a padding or spacing setting under Layout that you can reduce or remove.

    Please give that a try and let me know how it goes. We are here to help if you run into any issues.

    Have a great day ahead!

    Plugin Support BSF – Ravi Gojiya

    (@ravigojiya)

    Hi @mooer,

    Glad to hear that! We will make sure to share an update here once the new version is out, so you know when to update.

    In the meantime, could you mark this topic as Resolved? It helps other users searching for similar issues find the thread more easily. You can do that using the toggle at the bottom of the thread.

    Thank you for your patience and for the kind words!

    Have a wonderful day ahead!

    Plugin Support BSF – Ravi Gojiya

    (@ravigojiya)

    Hi @goddamnnoise and @mmeid72,

    Good news! We have released a proper fix for this in Spectra Free v2.19.26. Please update the plugin, and the warnings in your server logs should stop.

    @mmeid72, thanks for sharing the manual fix in the meantime. That was helpful for anyone who needed an immediate workaround before the update landed.

    Please update to v2.19.26 and let us know if everything looks good on your end. If so, could you mark this topic as Resolved? That helps other users with the same issue find the solution faster.

    Have a nice day ahead!

    Plugin Support BSF – Ravi Gojiya

    (@ravigojiya)

    Hi @tricktrommler,

    Thank you so much for taking the time to write this, it really means a lot!

    It is great to hear that Spectra has been a good fit for your work, especially coming from someone who deals with performance focused builds day in and day out. Clean, lightweight code is something we take seriously at Brainstorm Force, and knowing that it holds up in demanding, real world workflows like yours is exactly the kind of feedback that keeps the team motivated.

    And yes, support is something we genuinely care about. We believe a great plugin should come with great support, so hearing that you’ve had such a positive experience on both fronts makes our day.

    We will keep pushing to make Spectra better with every release. If you ever have a suggestion or run into anything, feel free to drop it here or reach out through our support portal. We are always listening.

    Have a wonderful day ahead!

    Plugin Support BSF – Ravi Gojiya

    (@ravigojiya)

    Hi @mooer,

    Thank you for reaching out and for sharing those screenshots. I can see exactly what you mean, and I appreciate the detailed illustrations.

    You are right that this is a bug. The Icon List block currently has issues when inserting links directly in the editor, which causes the backend editing experience to break visually, even though the frontend renders correctly. We apologize for the inconvenience this has caused.

    The good news is that this is already on our radar. With our upcoming major release, this bug will be fixed.

    On top of that, we are also introducing a significant improvement to the Icon List block as part of the same release. You will no longer be limited to plain text inside the list items. You will be able to add any custom block inside the link, such as a core Heading block, a Paragraph block, or even the Spectra Text block. This means you will be able to copy and paste text with links inside the Icon List without any issues.

    We appreciate your patience while we finalize the release. Please keep an eye out for the update.

    Have a great day ahead!

    Plugin Support BSF – Ravi Gojiya

    (@ravigojiya)

    Hi @mmeid72,

    Thank you for jumping in and sharing your suggested fix. We really appreciate the time you have taken to help the community.

    One small note for anyone reading this thread, we generally do not recommend editing plugin files directly. Any change made inside the plugin folder will be overwritten the next time Spectra is updated, and it can also cause unexpected behavior during future releases.

    The good news is that our development team has already picked this up. A pull request to address the issue inside zipwp-images-api.php is being raised at the moment, and the proper fix will ship in an upcoming Spectra release. That way you will be able to update normally and have everything resolved without any manual changes to the plugin files.

    In the meantime, if the warnings are filling up your debug log, you can keep WP_DEBUG turned on while setting WP_DEBUG_DISPLAY to false inside wp-config.php. That way, entries are still captured for review, but they will not show up on the front end for visitors.

    Have a wonderful day ahead!

    Plugin Support BSF – Ravi Gojiya

    (@ravigojiya)

    Hi @goddamnnoise,

    You are very welcome, and thank you for the kind reply.

    That sounds great. If the site does crash again and you suspect it is related to this, please share the fatal error message from the logs along with anything you noticed leading up to it. We will be happy to dig into it and figure out what is going on from there.

    Have a nice day ahead!

    Plugin Support BSF – Ravi Gojiya

    (@ravigojiya)

    Hi @goddamnnoise,

    Thanks for the detailed report and the analysis you have already done.

    I checked the code on our side, and you are correct. On line 471 of zipwp-images-api.php, the function calls explode() and reads index [1] without first checking that the URL actually contains a question mark. When an image URL comes through without a query string, explode() returns only one element, so reading the second one produces the warning you are seeing.

    About your other question, the ZipWP image library is a built-in part of Spectra. When Spectra is active, it adds a Stock Images option inside the WordPress Media Library that lets you search and insert images from sources like Pexels directly. That is why this code runs in the background even when you are not actively using ZipWP, and it is also why every Spectra installation has this file present.

    This has been confirmed as a valid bug on our side, and a fix is already being worked on. It will be included in an upcoming Spectra release.

    On the crashes you mentioned, a plain PHP warning of this type should not normally bring a site down, so the actual crash may be coming from a different source. If you can share the fatal error message from the logs along with the steps that led to it, we will be happy to look into that as well.

    Have a great day ahead!

    Plugin Support BSF – Ravi Gojiya

    (@ravigojiya)

    Hi Kevin,

    Thanks a lot for confirming, and apologies again for the trouble this one caused.

    You are absolutely right about the class_exists() calls, and we really appreciate you pointing out the exact problem with a working example on 3v4l. The static analysis suggestion is a good one, too. We will pass your PHPStan and Rector idea along to the dev team. Adding that kind of tooling to the release pipeline could genuinely help catch issues like this before they ship.

    Thanks again for the detailed reports throughout. They genuinely helped us turn the hotfix around as quickly as we did.

    Have a wonderful day ahead!

    Plugin Support BSF – Ravi Gojiya

    (@ravigojiya)

    Hi @danielg2goetz,

    Thank you so much for taking the time to leave this wonderful review! It truly means a lot to the whole team.

    Knowing that Spectra is part of your workflow across all your customer websites is something we are really proud of. That is exactly what we set out to build: a tool that professionals like you can rely on every single day without any hassle.

    We are also really glad the “few clicks to a stunning website” experience has been holding up in real projects. A lot of work goes into making the blocks flexible enough to handle everything from simple landing pages to complex layouts, so hearing that it is actually delivering on that promise is very rewarding for us.

    And thank you especially for the kind words about support. We genuinely care about every issue, big or small, and it is great to know that comes through. Your clients are in good hands with someone who takes their websites as seriously as you do, and we want to make sure we are always right there when you need us.

    We hope Spectra keeps making your projects easier and more enjoyable. If there is ever anything we can do better or any feature you would love to see, please do not hesitate to share it with us.

    Have a wonderful day ahead!

Viewing 15 replies - 1 through 15 (of 19 total)