Search Results for 'composer'

Hi,
Is there someway I can check that the theme updated correctly? After updating I ran the PHP compatibility checker and get incompatibility errors for visual composer and slider revolution. Here’s the notes for Visual Composer:
FILE: /nas/content/live/travel2next/wp-content/plugins/js_composer/include/templates/editors/partials/backend-shortcodes-templates.tpl.php
————————————————————————————————————————————————–
FOUND 0 ERRORS AND 3 WARNINGS AFFECTING 3 LINES
————————————————————————————————————————————————–
44 | WARNING | Possible use of ASP style opening tags detected. ASP style opening tags have been removed in PHP 7.0. Found: <%= type %>”>
45 | WARNING | Possible use of ASP style opening tags detected. ASP style opening tags have been removed in PHP 7.0. Found: <%= heading %></div>
47 | WARNING | Possible use of ASP style opening tags detected. ASP style opening tags have been removed in PHP 7.0. Found: <%= form_element %>
————————————————————————————————————————————————–

FILE: /nas/content/live/travel2next/wp-content/plugins/js_composer/include/templates/editors/popups/shared-templates/category.tpl.php
————————————————————————————————————————————————————-
FOUND 0 ERRORS AND 12 WARNINGS AFFECTING 12 LINES
————————————————————————————————————————————————————-
134 | WARNING | Possible use of ASP style opening tags detected. ASP style opening tags have been removed in PHP 7.0. Found: <%- post_id %>”
135 | WARNING | Possible use of ASP style opening tags detected. ASP style opening tags have been removed in PHP 7.0. Found: <%- title %>”
141 | WARNING | Possible use of ASP style opening tags detected. ASP style opening tags have been removed in PHP 7.0. Found: <%- title %></button>
149 | WARNING | Possible use of ASP style opening tags detected. ASP style opening tags have been removed in PHP 7.0. Found: <%- post_id %>"]” titl…
160 | WARNING | Possible use of ASP style opening tags detected. ASP style opening tags have been removed in PHP 7.0. Found: <%- id %>”>
162 | WARNING | Possible use of ASP style opening tags detected. ASP style opening tags have been removed in PHP 7.0. Found: <%- thumbnailUrl %>” alt=””…
165 | WARNING | Possible use of ASP style opening tags detected. ASP style opening tags have been removed in PHP 7.0. Found: <%- previewUrl %>” data-tit…
167 | WARNING | Possible use of ASP style opening tags detected. ASP style opening tags have been removed in PHP 7.0. Found: <% if (!downloaded) { %>
171 | WARNING | Possible use of ASP style opening tags detected. ASP style opening tags have been removed in PHP 7.0. Found: <% } else if (downloaded &&…
175 | WARNING | Possible use of ASP style opening tags detected. ASP style opening tags have been removed in PHP 7.0. Found: <% } %>
180 | WARNING | Possible use of ASP style opening tags detected. ASP style opening tags have been removed in PHP 7.0. Found: <%- title %></span>
182 | WARNING | Possible use of ASP style opening tags detected. ASP style opening tags have been removed in PHP 7.0. Found: <%= status %>
————————————————————————————————————————————————————-

FILE: /nas/content/live/travel2next/wp-content/plugins/js_composer/include/templates/teaser.html.php
————————————————————————————————————————————————————
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
————————————————————————————————————————————————————
84 | WARNING | Possible use of ASP style opening tags detected. ASP style opening tags have been removed in PHP 7.0. Found: <%= id %>” src=”<%= url %>”…
————————————————————————————————————————————————————

FILE: /nas/content/live/travel2next/wp-content/plugins/js_composer/js_composer.php
———————————————————————————-
FOUND 1 ERROR AFFECTING 1 LINE
———————————————————————————-
220 | ERROR | Visibility for magic method __sleep must be public. Found: private
———————————————————————————-

Slider revolution:
FILE: /nas/content/live/travel2next/wp-content/plugins/revslider/includes/slider.class.php
————————————————————————————————————————–
FOUND 1 ERROR AFFECTING 1 LINE
————————————————————————————————————————–
2231 | ERROR | ‘clone’ is a reserved keyword introduced in PHP version 5.0 and cannot be invoked as a function (T_CLONE)
————————————————————————————————————————–

FILE: /nas/content/live/travel2next/wp-content/plugins/revslider/includes/output.class.php
————————————————————————————————————————-
FOUND 1 ERROR AFFECTING 1 LINE
————————————————————————————————————————-
436 | ERROR | ‘clone’ is a reserved keyword introduced in PHP version 5.0 and cannot be invoked as a function (T_CLONE)
————————————————————————————————————————-

Hi Catalin,

Thanks for your answer, before I put my developer on this, I would like to understand :

If I press “modifiy” on the top bar menu of a category, I see this http://www.screencast.com/t/dgvl5gt12xN9. I dont have visual composer, neither Yoast available. Same thing for the tags.

However, if I press “modify” on the top bar menu of a page. I see this http://www.screencast.com/t/SYwCGpmi13, with visual composer and Yoast available.

Regarding to you, the reason why visual composer and Yoast are not available on “modify” command, would be a wrong setting as described here : https://forum.tagdiv.com/system-status-parameters-guide/ ?

Or could there be another issue somewhere else ?

1000 Thanks in advanced 🙂

I added that code and everything is up to date on the latest versions. It seems to be happening when I add a widgetized widget to the visual composer. The widgetized widget disappears in the visual composer and you can’t see it.

Yes, just leaving visual composer and newspaper plugins.

I just wish the excerpt would be published on the page.

On creating new pages, the tools to edit ain’t there, and option the use visual composer to build the page isn’t there too.

See Screenshot:

https://www.dropbox.com/s/rdeadsv4z1rnu93/Screenshot%202017-02-22%2013.38.07.png?dl=0

https://www.dropbox.com/s/l4apwdrk1jo2vrm/Screenshot%202017-02-22%2013.43.02.png?dl=0

I dont see this code define( ‘WP_MEMORY_LIMIT’, ’64M’ ); in the wp-config.php file. I added it to the config file but it still isnt changing anything in the usual composer. Could there be something else I need to add?

• This reply was modified 9 years by bigredfro.
• This reply was modified 9 years by bigredfro.

Hi Catalin,
The eternal problem with the Speed Booster plugin is not how Google interprets/see the code, the problem is in the Speed Booster coding.

Please talk with your developer and look seriously a little closer to the problem because all that warnings are related with the Google fonts implemented in this plugin, “Speed Booster”.

Examples of rendering blocking and when appear:

• since I bought your theme, I remove completely any Google font and never I receive that warning; if I use your default font or any other, yes I receive warnings about render blocking.
• when featured image is disabled for posts
• when blockquote is used in comments
• when the post have too much comments (more than 200)

I hope this information arrives to your developer.

I’ve always used your theme without any other untested plugin (only Yoast Premium, Visual Composer & Speed Booster), not even WP Super Cache.

I have to say that removing the Google font, allways we had 99/100 score (both PC & mobile) into PageSpeed Insights and the site charge in 0,4 sec.

Maybe your developers will implement some default option to disable the Google fonts from the panel settings (I think we are many users that keep asking for this).

¡Thank you and best to all!