BSF - Ravi Gojiya
Forum Replies Created
-
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!
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!
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!
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!
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!
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!
Forum: Reviews
In reply to: [Spectra One] Great Support Even for Hosting‑Related IssuesHi @madwealth,
Thank you so much for taking the time to share this! It truly means a lot to us.
We are really glad we could help you track down the cause of the JSON error. Situations like this can be tricky because the root cause is not always within the product itself, but our goal is always to make sure you have a clear answer and a clear path forward, regardless. Knowing that the team’s responsiveness made a difference is something we genuinely appreciate hearing.
If you ever need help again, please do not hesitate to reach out. We are always happy to help!
Have a nice day ahead 😊!
Hi Kevin, we have good news!
We were able to reproduce the issue and confirmed it was caused by a class naming conflict introduced in 2.19.23. A hotfix has already been released as Spectra 2.19.24, which resolves this.
Please update to 2.19.24 from your Plugins page and let us know if everything is working fine on your end. If it does, we would appreciate it if you could mark this topic as Resolved.
We are sorry for the disruption this caused and appreciate your patience.
Have a great day ahead!
Hi Kevin,
Thank you for your patience while we looked into this.
We were able to reproduce the issue internally. It is caused by a class naming conflict between a library bundled in Spectra 2.19.23 and another plugin active on your site. The fix has already been identified and will be included in our upcoming update.
In the meantime, please continue using Spectra 2.19.22 as a workaround.
If you cannot wait for the update and need the fix right away, please open a support ticket at https://support.brainstormforce.com/forum/ and we will share a patched build with you there.
We are sorry for the trouble this caused. Thank you for helping us catch it.
Have a nice day ahead!
Hi Kevin,
Thank you for reaching out and for including the full error trace.
We are sorry to hear that the update caused trouble on your site. We were not able to replicate this on our end with version 2.19.23, so we would like to gather a bit more information to dig into this further.
Before anything else, it is worth trying a clean reinstall of Spectra. Sometimes, an incomplete file extraction during an auto update can cause class-not-found errors exactly like the one you are seeing.
Here is how to do it:
- Revert to 2.19.22 if you are not already on it
- Deactivate and fully delete Spectra from your Plugins page
- Reinstall it fresh from the WordPress plugin directory
- Check if the error still occurs
If the error persists after a clean reinstall, could you please share the following so we can investigate further:
- Your WordPress debug log. You can enable debug logging by following the steps at https://developer.ww.wp.xz.cn/advanced-administration/debug/debug-wordpress/
- A full list of your active plugins
- Your PHP version and WordPress version
This will help us narrow down what might be unique to your environment. Looking forward to hearing back from you.
Have a wonderful day ahead!