• Resolved Amanda

    (@rocketkiddo)


    Wasted 2 hours creating a nice visual story to get this error.

    I use Cloudflare.
    No error in Site Health, Rest API disabled.

    When this will be fixed?

Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Author Pascal Birchler

    (@swissspidy)

    Hi @rocketkiddo

    Thanks for reaching out! Sorry to hear you’ve lost 2 hours of work.

    Like the Gutenberg block ediitor, the Web Stories editor relies on the REST API to be enabled and fully functioning. So if you disable the REST API it cannot work at all.

    I’ll see if we can add some detection to the editor for the cases where the REST API is disabled, but we cannot change this requirement.

    Thread Starter Amanda

    (@rocketkiddo)

    Nothing works.

    Lost all the work after getting errors, can’t even save drafts.

    What’s weird is that when I’ve used your templates without any changings I could publish the story… Tried again, with the same template, changed few things (text, images), and again the error pop-ups.

    Why have you released the plugin without testing it properly?
    These are not “hidden bugs” or something… stop wasting my time with your buggy plugin and hire some legit people that know their stuff

    • This reply was modified 4 years, 1 month ago by Amanda.
    Plugin Author Pascal Birchler

    (@swissspidy)

    Again, sorry to hear it’s not working on your site.

    This kind of incompatibility can be caused by many different things. A disabled REST API won’t work, of course, but there can also be conflicts with plugins or firewalls.

    As mentioned on your review already, the plugin runs successfully on thousands of other sites, thanks to rigorous testing over many months. And it would be awesome if we could add your site to this list one day as well.

    Now, no-one forces you to “waste your time” with this plugin, and I understand if you just want to abandon the plugin for the time being. However, we cannot fix bugs if we don’t know about them. So it would be great if you could collaborate with us here to find the actual bug.

    For this, would you be open to share your Site Health information? If you wish to share privately you can use this form. With this we can further test for any incompatibilities.

    Thread Starter Amanda

    (@rocketkiddo)

    “Now, no-one forces you to “waste your time” with this plugin”

    Very professional for someone who has to deal with customer support.

    It’s typical for someone to just see the bright side and refuse to look on the other side. Have you searched on public forums, platforms? People complain about your plugin and you have no idea how to fix these issues.

    You are asking for something unrelated with this issue, like Site Health information could help you… how the hell a “software engineering” or how do you guys call yourself depends on Site Health to fix plugin issues.. lol.

    https://ibb.co/19YZJmP

    Here is the screenshot good luck with fixing the issue with this.

    I already gave you some useful information:
    – I use Cloudflare
    – Got Rest API disabled
    – Using your templates without any changes did work, made some small changes couldn’t publish the story.

    You just ask people to disable plugins like that’s the fix for your issues…

    Keep repeating yourself that this plugin works on thousands of sites, eventually, all problems will fly away…

    • This reply was modified 4 years, 1 month ago by Amanda.
    • This reply was modified 4 years, 1 month ago by Amanda.
    Plugin Author Pascal Birchler

    (@swissspidy)

    As previously mentioned, you need to enable the REST API for the Web Stories plugin to work correctly. It’s a prerequisite.

    I am not denying that there’s plenty of things we can improve in the plugin (which we are committed to doing!), I just wanted to give you an idea of how they depend on the context of every user’s site.

    THat’s why the Site Health information is valuable for us. This way we can find possible conflicts with other plugins and determine how we can fix them. FWIW, I was referring to the data under the “Info” tab in Site Health, not the “Status” part you shared the screenshot of.

    Thread Starter Amanda

    (@rocketkiddo)

    I was about to say that I’ve got the Rest API enabled, I don’t know why I typed disabled everytime, sorry for the misunderstanding.
    I’ve just uploaded the site health info privately.

    What pisses me off is that your plugin doesn’t even save drafts because of this issue and losing 2 hours made me lose my nerve. Hope you make that works and I’ll change my 1-star review.

    Plugin Author Pascal Birchler

    (@swissspidy)

    Thanks a lot for sharing your Site Health info! We’ll take a look and get back to you as soon as possible.

    Just two small follow-up questions:

    – Are you using any of Cloudflare’s firewall features?
    – Have you already tried troubleshooting the Web Stories plugin using the “Health Check & Troubleshooting” plugin?

    This will help us to further narrow this down.

    Hi Pascal,

    We’re having the same issues where it says “failed to save the story”.

    What information do you need me to send to you?

    Thank you

    Plugin Support Luckyna San

    (@luckynasan)

    @alxmiller Thank you for reporting! Per forum guidelines please open a new support topic with information related to your issue.

    You can inform us if you are using any firewall services or if you’ve tried troubleshooting the Web Stories plugin using the “Health Check & Troubleshooting” plugin to help narrow down what may be causing these issues.

    Thank you.

    Plugin Author Pascal Birchler

    (@swissspidy)

    Hi @rocketkiddo & @alxmiller,

    In the new version 1.1.0 of the plugin we’ve included an experimental solution for this issue that allows you to keep using the plugin while still being fully protected by Cloudflare.

    Because it’s still experimental, it takes a couple of steps to enable this:

    1. Add define( 'WEBSTORIES_DEV_MODE', true ); to your **wp-config.php** file
    (somewhere before the /* That's all, stop editing! Happy publishing. */) line)
    2. In your WordPress admin, go to **Stories** -> **Experiments**
    3. Toggle the **WAF Compatibility** checkbox and save the changes.
    4. Create a new story!

    Could you try this and let us know if this works for you?

    Meanwhile, we’re working hard on stabilizing this feature in time for our 1.2.0 release so you don’t have to do these steps anymore.

    Thanks for your cooperation and patience!

    shogunteam

    (@shogunteam)

    I have the exactly the same issue as rocketkiddo. When I use one of the templates, then I can publish and save the story. As soon as I edit it, it does not work any more. Just waste of time.

    Plugin Author Pascal Birchler

    (@swissspidy)

    @shogunteam Are you using Cloudflare or Sucuri’s Web Application Firewall? If so, please follow the step right above your comment for a workaround. If not, please open a new support topic and share more details about your site there.

    Plugin Support Luckyna San

    (@luckynasan)

    @rocketkiddo Hello! We’ve recently released version 1.2.0 of Web Stories which includes the work to stabilize WAF compatibility. Could you please update to the latest version and let us know if there are any issues? Thank you.

    Plugin Support Luckyna San

    (@luckynasan)

    @rocketkiddo Closing this topic as resolved since we haven’t received a response. Please don’t hesitate to open a new support topic if you continue to experience any issues. Thank you!

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Failed to save the story’ is closed to new replies.