Problem after updating WPBakery page builder and x-theme

Support
#1

Hi, after updating Visual composer to the latest version (5.5) and x-theme to the 6.1.6, I have a problem with post masonry grid: it doesn’t work anymore. Also, there some other problems with post grids.

I have created a custom grid with grid builder and then apply it to post masonry grid with a custom post type. Before updating, all has working well.

I have tried to disable plugin one by one, but nothing is changed.

The pages with this problem are two:

On the first page Chrome console give me this errors:

Failed to load resource: the server responded with a status of 500 (Internal Server Error) /wp-admin/admin-ajax.php:1

On the second page, when I click on button “Continua a leggere”:

POST http://millennium.alecss.it/wp-admin/admin-ajax.php 500 (Internal Server Error)
send @ jquery.js?ver=1.12.4:4
ajax @ jquery.js?ver=1.12.4:4
VcGrid.ajax @ vc_grid.min.js?ver=5.5:1
vcGridStyleLoadMore.render @ vc_grid.min.js?ver=5.5:1
VcGrid.initStyle @ vc_grid.min.js?ver=5.5:1
init @ vc_grid.min.js?ver=5.5:1
VcGrid @ vc_grid.min.js?ver=5.5:1
(anonymous) @ vc_grid.min.js?ver=5.5:1
each @ jquery.js?ver=1.12.4:2
each @ jquery.js?ver=1.12.4:2
$.fn.vcGrid @ vc_grid.min.js?ver=5.5:1
(anonymous) @ vc_grid.min.js?ver=5.5:1
i @ jquery.js?ver=1.12.4:2
fireWith @ jquery.js?ver=1.12.4:2
ready @ jquery.js?ver=1.12.4:2
K @ jquery.js?ver=1.12.4:2

I’ve noticed that also if I don’t click on button, there are loading gif active at the bottom, as something has to be loaded.

Seems to be a problem caused by a jQuery conflict with VcGrid script. Never happend this before now.It’s a shame, because now visual composer has become really fast like never before.

I hope you can help me resolve this issue.
I’m about to go out with the site in production, so you can understand how critical the situation is. :cold_sweat:

Thank you very much

#2

Hi @Ghiotto,

Thanks for reaching out and sorry to hear you’re having this issue.

I checked and the reason it triggers that error is from the Visual Composer itself.

[21-Jun-2018 10:50:34 UTC] PHP Fatal error: Uncaught exception 'Exception' with message 'WPBMap::modify can be called only in default scope' in /home/***/***/wp-content/plugins/js_composer/include/classes/core/class-wpb-map.php:708

I checked our list and there is no known issue related to this. Do you still have the older version for Visual Composer? Please clone your site into staging and let’s do the update and testing there, I like to compare the two and a working copy will be a lot helpful.

Thanks!

#3

Hi, thanks for response. The site is already on staging, let me copy on another staging domain.

Do I proceed to install an older version of visual composer or do I leave an exact copy of the site and then you’ll install older visual composer?

Let me know

#4

Hello There,

Since this is already in staging site, could we disable some of the plugins like the caching and others so that we can investigate further? And maybe if you can re install the old version so that we can check it as well.

Thanks.

#5

Hi, I’m making a site clone on another staging domain, so you can compare its behaviour with the latest visual composer and an older version as @Rad have asked to me. In the next hours I’ll be able to give you access to the new staging area.

PS: I have already tried to disable all plugins, including cache plugin, but nothing is changed.

#6

Hi, I have made a clone and you can find it here: http://staging.alecsslab.com
Same credentials for wordpress backend.
I have installed visual composer version 5.4.7 and Post masonry grid and Post grid were come back to work as expected.

Let me know how I can use the new 5.5 visual composer (faster and better).

Thanks so much

#7

Hi Alessandro,

Thank you for all the information. I checked the case and could not find a cause of the issue and actually, it seems to be a problem of the Visual Composer on your server as I could not find any problems in our issue tracker and a brief Google Search.

I did install the WP-Serverinfo plugin which you can access from Bacheca > WP-Serverinfo and there is one point that might be problematic:

I suggest that you contact your hosting service provider and ask them to make sure that the value for that option is 300.

The main error is the error 500 and it is an Internal Server error I suggest that you follow the steps below:

  1. Enable the WordPress Debug mode so instead of the error 500, you see the actual problem.
  2. If it does not show the message still, contact your hosting service provider and ask them to check the error log and give you the exact error which causes the problem.

Please consider that I totally understand that this is a difference between versions of the Visual Composer, but maybe the new version is more demanding and your server cannot serve the plugin correctly and that is why the error 500 occurs. We can not be sure unless you get the exact error log to see what is the problem.

Thank you.

#8

Hi, thanks for response.
I have made another clone and changed server. I have also set Max-execution_time at 300, but the problems remains.

This is the log of wordpress debug (limited at today):

25-Jun-2018 09:58:04 UTC] PHP Notice:  Undefined variable: fade_duration in /web/htdocs/www.millenniumcenter.info/home/live/wp-content/themes/x/framework/functions/plugins/visual-composer.php on line 5173
[25-Jun-2018 09:58:04 UTC] PHP Notice:  Undefined variable: bg_color in /web/htdocs/www.millenniumcenter.info/home/live/wp-content/themes/x/framework/functions/plugins/visual-composer.php on line 5234
[25-Jun-2018 09:58:04 UTC] PHP Notice:  Undefined variable: fade_duration in /web/htdocs/www.millenniumcenter.info/home/live/wp-content/themes/x/framework/functions/plugins/visual-composer.php on line 5173
[25-Jun-2018 09:58:04 UTC] PHP Notice:  Undefined variable: bg_color in /web/htdocs/www.millenniumcenter.info/home/live/wp-content/themes/x/framework/functions/plugins/visual-composer.php on line 5234
[25-Jun-2018 09:58:08 UTC] PHP Fatal error:  Uncaught exception 'Exception' with message 'WPBMap::modify can be called only in default scope' in /web/htdocs/www.millenniumcenter.info/home/live/wp-content/plugins/js_composer/include/classes/core/class-wpb-map.php:708
Stack trace:
#0 /web/htdocs/www.millenniumcenter.info/home/live/wp-content/plugins/js_composer/include/classes/core/class-vc-mapper.php(207): WPBMap::modify('vc_row', Array, '')
#1 /web/htdocs/www.millenniumcenter.info/home/live/wp-content/plugins/js_composer/include/classes/core/class-wpb-map.php(858): Vc_Mapper->callElementActivities('vc_row')
#2 /web/htdocs/www.millenniumcenter.info/home/live/wp-content/plugins/js_composer/include/classes/core/class-wpb-map.php(406): WPBMap::setElementSettings('vc_row')
#3 /web/htdocs/www.millenniumcenter.info/home/live/wp-content/plugins/js_composer/include/classes/shortcodes/shortcodes.php(1450): WPBMap::getShortCode('vc_row')
#4 /web/htdocs/www.millenniumcenter.info/home/live/wp-content/plugins/js_composer/include/helpers/helpers.php(1311): Vc_Shortcod in /web/htdocs/www.millenniumcenter.info/home/live/wp-content/plugins/js_composer/include/classes/core/class-wpb-map.php on line 708

It’s so strange that 3 different hosting services have the same problem. It’s ok the new version of visual composer can be more demaning of resources, but it’s strange that on all 3 different hoting it doesn’t work. I think instead there could be some coflict, don’t you think?

Tnanks for your effort, let me know

#9

Hi @Ghiotto,

Maybe the error is copied from the main site? The home page and /negozi/ doesn’t display internal error any more on my end. It loads the other items of the grid, without error compared to the live site. Perhaps, this is host related.

Please try your staging and you’ll see what I mean.

Thanks!

#10

Hi @Rad maybe you don’t have followed all the conversation. On the staging site (http://staging.alecsslab.com/) I have installed the visual composer 4.5.7, i. e. an older version as you have asked for comparision reason with the main site that have installed the latest version of visual composer. Do you understand?

My degub log, yes, is from main site were it’s installed visual composer 5.5.

#11

Hi @Ghiotto

Looks like this is a known issue and it has been reported to the plugin author, their development team is still investigating this issue though!

Thanks.

#12

Ok, but it doesn’t seem the same issue. That user add a new param to vc, and then visual composer generates that error.

#13

Hey Alessandro,

Another support member here. I wanted to check your setup but your sites take a very long time to load so I wasn’t able to load them.

I’d like to add here that the Post Grid element is native to VC. To quickly check if the issue is coming from X and/or Cornerstone, please try deactivating X Integrateion in WPBakery Page Builder > X Integration. If the feature works after this, it could be a conflict with X Integration. Once you disable X Integration, it is equivalent to using VC natively so if it still does not work, the bug is most probably within VC.

Also, in case you don’t know yet, X Integrated VC elements are the shortcode interface of the shortcodes in X so by deactivating X Integration, you won’t be able to add X elements though they’ll still work in the front-end since they’re just shortcodes.

Thanks.

#14

Ok, I have disable X integration and now visual composer 5.5.1 works on http://millennium.alecss.it/ and the error Failed to load resource: the server responded with a status of 500 (Internal Server Error) /wp-admin/admin-ajax.php:1 is disappeared.

However this is a problem because I have styled all visual composer elements integrated with X and if I disalble integration I lost all my website design.

Could be a cornerstone conflict?

Can you investigate more deeper about this issue?

For helping your work, I have tried to install X theme 6.1.6 and Visual composer 5.5.1 on a new Wordpress installation. http://development.alecsslab.com/pagina-di-esempio/

Here visual composer is working also with x integration active. So on http://millennium.alecss.it/ must be some conclift.

PS: @christian_y the site is loading well, try again http://millennium.alecss.it/

#15

We could not consider this a general conflict because I tested the same setup in my dummy sites and the Post Masonry Grid loads. I investigated deeper but I’m sorry I have not determined what is causing the issue.

Is it possible that you create a clean install of WordPress with only X, Cornerstone and Visual Composer? We need to test if the issue will persists. You can try setting up a free site at http://poopy.life/.

Instead of pursuing the Post Masonry VC element, is it also possible that you consider using one of the bundled grid plugins in X instead. That would be the quickest solution if you need X Integration for your site.

Also, your site loaded when I connected to a different network but my antivirus prevented me from entering so I checked with another computer (see secure note).

Thanks.

#16

Yes, I know there is that problem on alecss.it domain. Hosting company say that the domain is clean and there are no maleware o viruses.

I have already set up a cleanwordpress intallation with X 6.1.6 and visual composer 5.5.1, I have given you the link in previous message. You can find the clean wp installation here: http://development.alecsslab.com

http://development.alecsslab.com/pagina-di-esempio/ in this page there’s a post masonry grid in action. I have installed faker press only for generates some content and use a dynamic post grid.

@Alaa I have checked my server error log and effectively I have found the same error that you have reported on codecanyon forum. My apologies. So, I’m waiting for a WpBakery fix, I hope a new plugin version resolves this issue.

However, let me know if you find something other about some conflict that I can eliminate.

Thank so much

#17

Hi @Ghiotto,

Yes, I will forward this thread to our developer so they could also look on it.

Thank you so much for your patience.

#18

Ok, WpBakery has updated his plugin to a new version, 5.5.2, and now the problems are gone. Everything has come back to work.

Thank you so much for support

#19

Hi @Ghiotto,

Happy to hear that.

Feel free to ask us again.

Thanks.

#20

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.