Update: I published, and even after publishing still got the error when attempting to use Nimble Builder. So apparently it’s a bug.
# SITE_URL: https://www.y42k.com/wp
# HOME_URL: https://www.y42k.com
# IS MULTISITE : No
# ACTIVE THEME : Customizr-pro Child 1.0.0
# PARENT THEME : Customizr Pro 2.4.9
# WP VERSION : 5.7.1
# PERMALINK STRUCTURE : /%year%/%monthnum%/%day%/%postname%/
# ACTIVE PLUGINS :
Akismet Anti-Spam: 4.1.9
Autoptimize: 2.8.3
Custom Sidebars: 3.31
GA Google Analytics: 20210211
Google XML Sitemaps: 4.1.1
Jetpack by WordPress.com: 9.6.1
Limit Login Attempts: 1.7.1
Nimble Page Builder: 3.1.2
Really Simple SSL: 4.0.14
reCaptcha by BestWebSoft: 1.61
Slideshow: 2.3.1
Smush: 3.8.4
WP Mail SMTP: 2.7.0
Yoast Duplicate Post: 4.1.2
PHP Version: 7.4.16
MySQL Version: 5.7.34
Web Server Info: Apache
WordPress Memory Limit: 40MB
PHP Memory Limit: 256M
PHP Upload Max Size: 32M
PHP Post Max Size: 32M
PHP Upload Max Filesize: 32M
PHP Time Limit: 30
PHP Max Input Vars: 1000
PHP Arg Separator: &
PHP Allow URL File Open: Yes
WP_DEBUG: Disabled
Show On Front: page
Page On Front: Home (#7013)
Page For Posts: Blog (#7010)
I can get to the Builder if I:
1. Create the draft
2. Open it in Preview
3. Edit with Nimble.
Poor workflow, if you ask me.
And I still have a problem that was introduced last week:
Once I get the post open in the Customizer to edit with Nimble, when I “Import” my standard .nimblebuilder file, the Customizer displays my home page instead of the post I’m working on. I have to Publish, then exit the Customizer, then find the post and finish editing.
This bug was introduced recently. WP/themes/plugins are all updated before I do any editing. Last Sunday is when I first saw it.
Finally managed to get the page published.
https://www.y42k.com/2021/05/02/tardis-jukebox-may-4th-2021/
This was all working fine until a week ago. But the way things work right, now if the workflow issues aren’t fixed, the Builder isn’t worth the hassles.
Thanks for reporting the problem.
Yes this alert message has been introduced in the last version because various problems had been reported by different users when trying to build a draft post or page. The typical problems were :
1) duplicated sections created when inserting one
2) preview refreshed to home page instead of the edited post or page.
The problem also occured on posts with the ‘future’ status ( scheduled posts ).
This is due to a limited support of WP live customizer for posts with those status.
But the current implementation is too restrictive because it only allows NB to work on posts with the “publish” status. This doesn’t cover the common case when a user doesn’t want the post to be visible on the site. The next update will implement a solution to this problem by allowing users to build with Nimble Builder when posts are published privately, which will be similar to using the ‘draft’ status workflow.
Until a bit more than a week ago, I have to assume NB was working properly with drafts for most people, as it was for me. Now you’re asking EVERYONE to break how WP works in order to use NB? Forcing people to publish instead of getting your tool to work properly with drafts is NOT a reasonable solution.
I’m trying to find solutions. Not to force anyone to do something, which by the way doesn’t break how WP works.
The problem when using Nimble Builder on drafts wasn’t reported until recently. I don’t know if it’s due to a change recently introduced in WordPress.
In the version recently released of Nimble Builder, a post had to be published to be edited with Nimble Builder. This was an incomplete solution because it did not allow user to use Nimble Builder on a unpublished post.
The latest release (today) let users edit with Nimble Builder on a privately published post, which is the best temporary solution I could come with, while trying to understand why working on a draft post breaks Nimble Builder.
I’m sorry if it changes your usual workflow, but I’m really trying to do my best to find solutions for users. Adapting to the fast evolving WordPress software is not easy. Exploring a permanent fix takes time. Thank you for your understanding.
Update : good news, I finally found the source of the problem and fixed the problem.
This was a regression introduced in the plugin recently when implementing a solution for another problem.
You should now be able to use your previous workflow.
Many thanks for reporting your issue on the forum. It greatly helped ! 👌 🙏
