HI,
I am using Vantage Premium theme. I create pages using page builder. I insert Nextgen pro galleries into the page builder element using the visual editor widget. In visual editor I use the normal green nextgen button to insert and customise gallery. All fine so far. The problem comes in when I add a row or widget below this gallery. Noting shows. If I replace the gallery inserted into the visual editor widget with the equivalent shortcode the problem goes away. It looks like this has something to do with the way visual editor (or the theme) processed the nextgen gallery.
If you look at the url below you can see the format I use. The first page builder row is two widgets, the text and the slide show. The next row is the thumbnails, the next row is the project team table. The widgets are all visual editor widgets. If I insert the nextgen gallery into the thumbnail row (v.e. widget) using the nextgen in place editor the project team row disappears. If I use a nextgen shortcode instead of the in-place editor to insert the thumbnails the project team row shows.
URL: http://jma.za.net/project/contemporary/head-road-glamour/
Hi Rob
Thanks for reporting this.
There are a few instances in Page Builder where using a shortcode over a widget resolves a bug like this. I can think of two others, one with Gravity Forms and another with Meta Slider. A challenge like this would need to be taken up with NextGEN. They’d need to decide whether it’s something they are willing to look into or not. As the popularity of Page Builder grows we’re seeing more and more plugin developers come aboard and get their plugins fully compatible. Hopefully, moving forward, this will be the case with NextGEN. In the case of a plugin developer needing us to look into an aspect of Page Builder with regards to a bug they’re facing we’re of course more than willing to do so. In that case we’d chat with the developer in question via email. In summary, a bug like this would unfortunately need to be investigated from the plugin authors side.
Hi Andrew,
Thanks for your prompt reply. I just want to check you have understood my query properly. The widget I am using in all cases above is the Visual Editor widget. Where you say “using a shortcode over a widget resolves a bug” – do you mean by widget here the Nextgen in place editor. This is not a widget really but an element in the content that pulls up a gallery as a more user friendly alternative to a short code. I will post your reply to nextgen support. I hope I am not going to end up falling between two, maybe three plugin authors each passing responsibility to the other.
Were the visual editor widget in the page builder element working exactly like posting normal content in the normal tinymce editor the nextgen in-place editor should work. Something is clearly different about how it is interpreted when it sits inside a widget in a page builder element. Does this mean page builder/visual editor is not completely transparent?
Thanks for your attention and response.
Rob
Apologies, where I’ve said widget, in this case I’m referring to the button that NextGEN adds to the TinyMCE toolbar.
Black Studio TinyMCE is based on the WordPress Visual Editor but yes, there is a lot more going on there to make that editor function as a widget. On top of that the widget (Visual Editor) is then being used within Page Builder which isn’t a regular widget area, this adds another level of complexity.
We run a small overall team and an even smaller development team. This means we unfortunately only have so much time to investigate Page Builder plugin clashes or bugs. As Page Builder progresses towards version 2.0 and we perhaps bring some sort of premium (monetised) aspect to the plugin we’ll be able to dedicated more resources towards actively investigating these kinds of challenges. We are currently working with plugin authors at the moment on major compatibility related issues as well as any authors that seek our assistance. In almost every case though that we’ve seen in the past, the fix required has needed to come from the plugin developer and not from within Page Builder. Keeping in mind that similar plugins cost anywhere from $28 to $55 we hope you can appreciate our position.
HI Andrew,
All good. I understand the limitations and appreciate your efforts as do I the value of the plugin. As long as this goes into the pipeline with all the other in-field use experience. This is a valuable extension of WordPress and begins to get a little closer to Drupal’s views and panels plugins which have become fundamental to its flexibility in presenting content.
Best
Rob
Thanks for your understanding and feedback. I’ve logged a ticket regarding the problem so we do have a record of it. Hopefully we we progress it’ll be something that gets sorted out.
(Perhaps also open a thread on the Black Studio plugin page on the directory, perhaps Marco might have some insight as to why this aspect of the plugin doesn’t work in the Visual Editor plugin).
Thanks again.