gfors

Mr.Ian…

Well, we used it on a few client sites. Some were best suited to parse the data, some not. The main thing is if you keep the html markup from the plugin when deactivating, you will have code in your content.

Thats fine, but the next time you use the regular visual editor, you might accidentally either manipulate or remove this code (which you only see in the text editor). Therefore it’s a bit of a minefield if you don’t know your way around html code.

The main upside to this plugin was that it used the bootstrap frameworks markup. So for instance for our client sites that we used the bootstrap framework on we could just add the pagebuilder and it would use the existing classes etc for columns and what not. So it fit seamlessly into the theme since they’re both using the same css.

I haven’t found any other pagebuilder that does this, and we have ended up making our own simple version for some clients who need it (for basic columns etc). Since I’ve lost all trust in using a third party plugin that has the potential of literally destroying all the content on the site without warning.

Since we don’t know what triggers this major issue, it’s also a risk leaving it active on a site. Without knowing, you could run into the same issue and end up with corrupt data, just by saving a post.

I would try and put it like this, if your theme uses bootstrap css, then you’re good with leaving the pagebuilder data when deactivating (since the code will work with your theme anyway). *But*, you’ll be left with code in your content. If your theme *doesn’t* use the bootstrap framework and you deactivate, this code will still be there but since the css is gone your site will probably look like crap ??

I can’t see any movement at all from devs in this issue.

At the moment the plugin feels abandoned, since ppl don’t seem to be receiving any help with this.

I would advise everyone to avoid it at the moment. We have deactivated and uninstalled it on all client sites that previously used it.

Getting the same thing on multiple sites.

Sometimes when updating the content on a page, hitting save, the page that reloads is just blank. After that, the page is broken. Ie everytime you try and go back to edit that page, just a blank screen. No errors, no wp_debug errors, no php errors. Just a blank page without anything at all (no data received).

Other pages works fine, but once this happens to a page, that particular page is broken and not possible to edit any more. Also the saved content that made the page “crash” has corrupted (halfway finished) data on frontend.

This is occurring on multiple hosts, multiple sites, with different configs. It’s not a plugin conflict, it doesn’t have to do with WP version (I haven’t updated these to 4.3 for instance). I’ve deactivated/reactivated plugin and tried all the “easy fixes” like clearing caches etc. Nothing.

This is a major issue with the plugin at the moment, and I wouldn’t advise anyone to use it at all until this is resolved.

Yup, I’m forcing SSL on wp-admin and /my-account/, and printing has broken completely due to using get_permalink which just uses the regular https:// and not https://

The above solution works great for me until there is a fix out.

/includes/class-wcdn-print.php on line #170 is the place to apply the fix

Any idea where this setting is? I’ve looked everywhere and tried every setting.

I’m having the same problem when passing multiple URL variables. I’ve switched of every setting in the plugin but nothing works. The only thing that works is disabling WordPress SEO all together.

+1!

Ok, so how would one show the actual value that is entered in the field?

For example I have made a dropdown list with Simple Fields, and I actually want to show the value that I enter for each drop-down option, and not “dropdown_num_4”.

The documentation on eskapism.se even shows that It’s supposed to show the value (your example with the color box, method 3, at https://eskapism.se/code-playground/simple-fields/tutorial-part-2/).

The example on your page wouldn’t output “green”, it would say something like “dropdown_num_2”.

Thanks for an awesome plugin, and please straighten this issue out. Otherwise it’s excellent!

EDIT: Managed to change the plugin myself to save the value and not the index to the post_meta in DB. But I think this should be the default behavior.