- NewspaperWhen tagDiv Composer is Not Working
- TutorialsSystem status parameters guide
- NewspaperCache plugin – install and configure
- NewsmagRequirements for Newsmag
- NewspaperRequirements for Newspaper
After that we were forced to return to the old theme because the new version of Newsmag had problems with the visual composer plugin becouse it used too much memory of the server, we decided to restore Newsmag, but without the visual composer plugin. It looks like a blog and not a magazine, but we hope that the TagDiv technical can solve this problem as soon as possible. We wanted to ask if the same problem occurred with the Newpaper Theme or is exclusive to Newsmag and if you plan to solve this problem.
thanks a lot
Hi All,
I’ve have noticed WPBakery Visual Composer has caused an issue with my theme when it comes to generating the Yoast Sitemap. It appears blank or memory errors are thrown everytime its active.
Is there any resolution?
Hi all,
I’m working to make the visual composer shim work better and it will be released here in 1-2 days.
@mrmorrison @mattrock – we had searched for the slowdown issue for almost one month now. It appears sometimes on bigger sites but we where unable to reproduce it here. Chirs S helped me by testing the visual composer shim and it looks like it works…. so the slow down can be from visual composer.
I’ve searched a lot in visual composer for what may cause this but it looks like I have to look deeper. The plugin is damn HUGE, it’s bigger than our themes and it’s not our code so it’s hard to debug. Especially that we did not find anything unusual on the callstack traces / memory traces.
Chris thanks a lot for the feedback and help, I will analyze the stats from the email and I will get back to you.
Hi, sorry to poke my nose in, only because I’ve been adjusting this stuff across our news network sites this month to “dial in” the best setting for the baby sites vs the big ones. Oddly when setting the memory in php.ini to 512MB, WordPress was saying “you only have 40MB allocated” … which made no sense.
Stupidly, and there should be no real reason to do this, I went ahead and added the pokey line to top of wp-config.php after the first commented stuff,
define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_POST_REVISIONS', 3 );
define( 'AUTOSAVE_INTERVAL', 160 );
and shazam, now WP says “I have 256MB” — even though the WP codex specifically says if you set the memory in php if would use more memory if needed (e.g., if I go to my php settings in my hosting panel it *says* 256MB, and the server DEFAULT was set to 256MB per site … WP was still saying 40MB which is the WordPres BUILT-IN default).
So, for purposes of paranoia, I *do* recommend you add the 256M line to your wp-config.php *and* set the level in your php settings…
this will
a) on server allow 256MB to be used for php
b) editing config file for WP, tells WP, you have more memory to actually play with since it apparently cannot figure this out … (!)
ALSO … you don’t need to use them, but I also include the limit drafts item in my example above, since that also seems to work better at “top” of wp-config.php file than at bottom.
Food for thought anyway 🙂
You can roll back without losing most settings except some widget go wonky, and home page might need to be re-saved, or checked for module/shortcodes not found in an earlier iteration — I think some codes changed between 1.5 and 1.6 if memory serves. Likely might need to refresh/tweak home page (not big deal really), and might need to drag some widgets back from “disabled” to the right places.
I did a backtrack from 1.7 to 1.6 when 1.7 first released, as our server went up to something like 150 or about 100x normal load (!). Simple. Luckily WordPress “transient” settings and dbase allow you to switch between themes and most settings recover — again except sometimes the widgets, and the menus – might need to go back to the “choose locations” and that takes 2 clicks.
I am going to try Radu’s “test shim” with one of our lesser sites running 1.6 — one of the sites I was baby-stepping before tackling the BIG one. Basically the site which dies with 1.7 has about 50x the traffic of the smaller sites, and because it’s been online for a decade it has a LOT of content, images, etc.
One nice thing about the “related posts” plugin I’m using, is that it only checks the past 365 days, not the past 3,500 days — and caches the result — so a tad more efficient on that bit of query.
More later …. can you say “shenanigans” (my word for 2015 …)
Hi,
1. Just the one form the wp-content > plugins folder and please always make sure you backup your WordPress and theme install: https://codex.wordpress.org/WordPress_Backups
2. Yes, best would be to disable all plugins, then delete the Visual Composer plugin and install within theme files > /plugins folder. Please use this guide: https://forum.tagdiv.com/update-the-visual-composer-plugin-wpbakery/
3. If you don’t use any cache plugins then go ahead without concerning this aspect.
4. 1. Edit your wp-config.php file and enter something like:
define('WP_MEMORY_LIMIT', '96M');
WordPress memory can be different to the server – you need to set this regardless of server memory settings
http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP
2. If you have access to your PHP.ini file, change the line in PHP.ini
If your line shows 32M try 64M:
memory_limit = 64M ; Maximum amount of memory a script may consume (64MB)
3. If you don’t have access to PHP.ini try adding this to an .htaccess file:
php_value memory_limit 64M
4. If none of the above works then talk to your host.
Thanks
Chris, I feel your pain… Same thing we were talking about (re server load) since Friday.
We are having the same problem with v1.71… maxing out resources we had to up memory in php.ini to 2048M just to function without to many errors. But not sure we can handle normal traffic of about 40k – 60k uniqe users per day.
The option to go back to old theme is not possible. We had to go head in on this one, with all the changes made to make our content fit NewsMag its just not an option.
Should we roll back to 1.6? We originally launched with 1.7 so I can not say for sure whether 1.6 would be stable.
php.ini
max_execution_time = 30 ; Maximum execution time of each script, in seconds
max_input_time = 60 ; Maximum amount of time each script may spend parsing request data
max_input_vars = 1000
;memory_limit = 512M ; Maximum amount of memory a script may consume (32MB)
memory_limit = 512M
Hello,
We are getting a lot of fatal errors and white screens (which require a reload or 2 before website displays.
We have a dedicated server with the following guts:
8X Intel(R) Xeon(R) CPU E3-1241 v3 @ 3.50GHz – Speed 3499.882 MHz – Cache 8192 KB
total used free shared buffers cached
Mem: 7999512 7368788 630724 80 383808 5755468
-/+ buffers/cache: 1229512 6770000
Swap: 8159228 275904 7883324
Total: 16158740 7644692 8514048
We also have 128MB allocated in the php.ini
We tried deactivating ALL plugins except visual composer.. This did NOT stop errors.
We tried deactivating all except those included from tagDiv.. This also did NOT fix it.
The website in question is: http://diaryofahollywoodstreetking.com
Any assistance fixing these errors and the huge use of server resources would be most appreciated !!
The errors seem to be caused from a broad mix of things. Here is a sample of errors here:
[01-May-2015 14:40:05 UTC] PHP Fatal error: Out of memory (allocated 43253760) (tried to allocate 18560 bytes) in /home/doahsk/public_html/wordpress/wp-content/plugins/js_composer/include/params/iconpicker/iconpicker.php on line 287
[01-May-2015 14:40:12 UTC] PHP Fatal error: Out of memory (allocated 46661632) (tried to allocate 32 bytes) in /home/doahsk/public_html/wordpress/wp-includes/cache.php on line 632
[01-May-2015 14:40:12 UTC] PHP Fatal error: Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0
[01-May-2015 14:40:13 UTC] PHP Fatal error: Out of memory (allocated 42729472) (tried to allocate 640 bytes) in /home/doahsk/public_html/wordpress/wp-content/plugins/js_composer/include/params/vc_link/vc_link.php on line 10
[01-May-2015 14:40:15 UTC] PHP Fatal error: Out of memory (allocated 28311552) (tried to allocate 20480 bytes) in /home/doahsk/public_html/wordpress/wp-includes/canonical.php on line 262
[01-May-2015 14:40:15 UTC] PHP Fatal error: Out of memory (allocated 8650752) (tried to allocate 12288 bytes) in /home/doahsk/public_html/wordpress/wp-includes/rewrite.php on line 327
[01-May-2015 14:40:21 UTC] PHP Fatal error: Out of memory (allocated 4718592) (tried to allocate 33920 bytes) in /home/doahsk/public_html/wordpress/wp-includes/query.php on line 2997
[01-May-2015 14:40:36 UTC] PHP Fatal error: Out of memory (allocated 21757952) (tried to allocate 1920 bytes) in /home/doahsk/public_html/wordpress/wp-includes/theme.php on line 572
[01-May-2015 14:40:36 UTC] PHP Fatal error: Out of memory (allocated 33292288) (tried to allocate 3072 bytes) in /home/doahsk/public_html/wordpress/wp-content/plugins/user-role-editor/includes/class-garvs-wp-lib.php on line 51
[01-May-2015 14:40:48 UTC] PHP Fatal error: Out of memory (allocated 25952256) (tried to allocate 49152 bytes) in /home/doahsk/public_html/wordpress/wp-includes/bookmark.php on line 246
[01-May-2015 14:40:59 UTC] PHP Fatal error: Out of memory (allocated 27000832) (tried to allocate 78080 bytes) in /home/doahsk/public_html/wordpress/wp-includes/script-loader.php on line 519
[01-May-2015 14:40:59 UTC] PHP Fatal error: Out of memory (allocated 43778048) (tried to allocate 196608 bytes) in /home/doahsk/public_html/wordpress/wp-content/plugins/js_composer/include/params/iconpicker/iconpicker.php on line 1478
[01-May-2015 14:41:01 UTC] PHP Fatal error: Out of memory (allocated 10747904) (tried to allocate 49152 bytes) in /home/doahsk/public_html/wordpress/wp-includes/canonical.php on line 121
[01-May-2015 14:41:02 UTC] PHP Fatal error: Out of memory (allocated 33030144) (tried to allocate 49152 bytes) in /home/doahsk/public_html/wordpress/wp-content/plugins/subscribe-to-comments-reloaded/subscribe-to-comments-reloaded.php on line 97
[01-May-2015 14:41:14 UTC] PHP Fatal error: Out of memory (allocated 24117248) (tried to allocate 49152 bytes) in /home/doahsk/public_html/wordpress/wp-includes/post.php on line 3231
[01-May-2015 14:44:36 UTC] PHP Fatal error: Out of memory (allocated 30670848) (tried to allocate 196608 bytes) in /home/doahsk/public_html/wordpress/wp-content/plugins/contact-form-plugin/contact_form.php on line 2108
[01-May-2015 14:44:44 UTC] PHP Fatal error: Out of memory (allocated 24117248) (tried to allocate 3072 bytes) in /home/doahsk/public_html/wordpress/wp-includes/post.php on line 5341
[01-May-2015 14:44:44 UTC] PHP Fatal error: Out of memory (allocated 37224448) (tried to allocate 120320 bytes) in /home/doahsk/public_html/wordpress/wp-content/themes/HSK/includes/td_config.php on line 1813
[01-May-2015 14:44:44 UTC] PHP Fatal error: Out of memory (allocated 29360128) (tried to allocate 3840 bytes) in /home/doahsk/public_html/wordpress/wp-includes/vars.php on line 70
[01-May-2015 14:44:45 UTC] PHP Fatal error: Out of memory (allocated 46399488) (tried to allocate 77 bytes) in /home/doahsk/public_html/wordpress/wp-content/plugins/js_composer/config/map.php on line 3702
[01-May-2015 14:44:45 UTC] PHP Fatal error: Out of memory (allocated 31195136) (tried to allocate 12288 bytes) in /home/doahsk/public_html/wordpress/wp-includes/post-template.php on line 1565
[01-May-2015 14:44:46 UTC] PHP Fatal error: Out of memory (allocated 45613056) (tried to allocate 262400 bytes) in /home/doahsk/public_html/wordpress/wp-content/plugins/js_composer/config/map.php on line 3576
[01-May-2015 14:44:47 UTC] PHP Fatal error: Out of memory (allocated 47448064) (tried to allocate 3072 bytes) in /home/doahsk/public_html/wordpress/wp-admin/includes/file.php on line 79
[01-May-2015 14:44:49 UTC] PHP Fatal error: Out of memory (allocated 35651584) (tried to allocate 1920 bytes) in /home/doahsk/public_html/wordpress/wp-content/plugins/xml-sitemap-feed/includes/core.php on line 972
[01-May-2015 14:44:56 UTC] PHP Fatal error: Out of memory (allocated 24379392) (tried to allocate 12288 bytes) in /home/doahsk/public_html/wordpress/wp-includes/post.php on line 5379
[01-May-2015 14:44:59 UTC] PHP Fatal error: Out of memory (allocated 27000832) (tried to allocate 196608 bytes) in /home/doahsk/public_html/wordpress/wp-includes/script-loader.php on line 243
[01-May-2015 14:45:09 UTC] PHP Fatal error: Out of memory (allocated 45613056) (tried to allocate 262400 bytes) in /home/doahsk/public_html/wordpress/wp-content/plugins/js_composer/config/map.php on line 3576
[01-May-2015 14:45:10 UTC] PHP Fatal error: Out of memory (allocated 2359296) (tried to allocate 3072 bytes) in /home/doahsk/public_html/wordpress/wp-includes/pomo/entry.php on line 69
[01-May-2015 14:45:11 UTC] PHP Fatal error: Out of memory (allocated 43515904) (tried to allocate 196608 bytes) in /home/doahsk/public_html/wordpress/wp-content/plugins/js_composer/include/params/iconpicker/iconpicker.php on line 379
[01-May-2015 14:45:17 UTC] PHP Fatal error: Out of memory (allocated 22544384) (tried to allocate 12288 bytes) in /home/doahsk/public_html/wordpress/wp-includes/meta.php on line 347
[01-May-2015 14:45:18 UTC] PHP Fatal error: Out of memory (allocated 32768000) (tried to allocate 49152 bytes) in /home/doahsk/public_html/wordpress/wp-content/plugins/subscribe-to-comments-reloaded/subscribe-to-comments-reloaded.php on line 97
[01-May-2015 14:45:18 UTC] WordPress database error Lost connection to MySQL server during query for query SELECT option_value FROM wp_options WHERE option_name = ‘home’ LIMIT 1 made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), wp_cookie_constants, get_option
[01-May-2015 14:45:18 UTC] WordPress database error Lost connection to MySQL server during query for query SELECT option_value FROM wp_options WHERE option_name = ‘hack_file’ LIMIT 1 made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), wp_get_active_and_valid_plugins, get_option
[01-May-2015 14:45:18 UTC] PHP Fatal error: Out of memory (allocated 43778048) (tried to allocate 49152 bytes) in /home/doahsk/public_html/wordpress/wp-content/plugins/js_composer/include/params/iconpicker/iconpicker.php on line 972
[01-May-2015 14:45:22 UTC] PHP Fatal error: Out of memory (allocated 28835840) (tried to allocate 3072 bytes) in /home/doahsk/public_html/wordpress/wp-includes/widgets.php on line 175
[01-May-2015 14:45:22 UTC] PHP Fatal error: Out of memory (allocated 2883584) (tried to allocate 72 bytes) in /home/doahsk/public_html/wordpress/wp-includes/plugin.php on line 85
[01-May-2015 14:45:23 UTC] PHP Fatal error: Out of memory (allocated 3670016) (tried to allocate 49152 bytes) in /home/doahsk/public_html/wordpress/wp-includes/formatting.php on line 3425
Hi im currently seeing this following error in my admin panel and im on a 32gb of ram server. please help not sure what to do my site is newswatch28.com
Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 48640 bytes) in /home/newswatch28/public_html/wp-includes/SimplePie/Item.php on line 1791
I have a very simple homepage where I use the visual composer. I have to use version 4.3.5, because every higher version will use to much memory (+100 mb) and slow down the site.
Is it possible to use another page builder with less functions or anything else?
I just need such a design:
slider -> ad -> posts -> load more button
and a sidebar
http://allaboutbelgaum.com/
From P3 profiler –
MySQL Queries: 154 queries avg.
Isnt this too much with my earlier theme it was just 70
Total Load Time: 21.0702seconds avg.
Site Load Time: 8.9674seconds avg.
Profile Overhead: 12.1028seconds avg.
Plugin Load Time: 4.4820seconds avg.
Theme Load Time: 2.0083seconds avg.
Core Load Time: 2.2097seconds avg.
Margin of Error: 0.2673seconds avg.
(21.0702 observed, 20.8028 expected)
Visits: 19
Number of PHP ticks: 35,890 calls avg.
Memory Usage: 102.55 MB avg.
MySQL Queries: 154 queries avg.
Hello.
I just moved my site to a VPS hosting and upon doing so I get a white screen with the visual composer plug in enabled.
I tried increasing my memory limit (google solution) and no help. Looking at my source some of the site is rendering but not all of it.
Basically nothing within the body tag. Any help would be appreciated.
Thanks
First, make sure you are uploading correct file — you want only the theme zip not the “all files” zip.
You can also upload the files via FTP, which is generally best way to do that.
But you may have to modify your PHP settings which is most common problem that gives that error.
————
try increasing your max_execution_time, your max_input_time, and your memory_limit, via the php.ini. You can often now do this via your hosting panel.
Maybe try something like:
max_execution_time = 120
max_input_time = 120
memory_limit = 64M
(note – memory limit of 128MB recommended if your host allows that)
Hi,
Since version 4.4.2 the Visual Composer plugin has doubled in size and also has several new features therefore uses more resources.
If you have access to your error.log file, you can take a look at it and see if there’s any data that can lead to a conclusion on why the VC plugin has crashed.
You can also try to increased the memory limit in php.ini, might be your issue.
Let us know how it goes.
Thanks
Hi,
Please try to increase the memory_limit in your php.ini file: http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP
Also make sure that you upload the newspaper.zip theme file not the newspaper-ft.zip file.
Let us know how it goes.
Thanks
I installed the theme and the required plug-ins, and when I clicked on something (I think the translation button) in the theme customizing panel, I got the following error.
“Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in /home/joronomo/public_html/wp-includes/query.php on line 3412”
I went into my file manager and renamed the theme, and my old theme was activated but now when I try to go into my WP admin, I just get that error message again. Please advise.
Hello,
I am trying to download the WordPress in-memory full page cache plugin (WP-FFPC) and whenever I try to activate it, it says this:
Plugin could not be activated because it triggered a fatal error.
Parse error: syntax error, unexpected T_FUNCTION in /home/content/b/o/l/bollenbach/html/livelovefruit/wp-content/plugins/wp-ffpc/wp-common/plugin_utils.php on line 188
What do I do about this? Is this something hosting-related?
Thanks!
OK so I decided to go into a zone to figure this out. I checked my PHP errors and noticed that it was a MEMORY ERROR.
And all this time I was wondering if plugins weren’t playing nice. So I increased memory and the world is all good.
If anyone was wondering, yes. I feel like an idiot for not checking something so simple.
Thanks for the help guys!
Often an issue with not enough memory allocated to php for your domain.
Ideally at least 128MB should be allocated, 256MB is better. Depending on your account they may limit that to as little as 16 or 32MB. Anything less than 64MB with modern themes, especially those using something like Visual Composer, and all those fun options like infinite loading, etc., all are queries via ajax and/or dbase.
First try increasing the memory allocated to php for your domain, or ask your host what the current limit it.
Hi,
Please check your php.ini memory allocation: https://forum.tagdiv.com/topic/demo-install-halts/
Hope this helps!
I just turned off whole bunch of stuff like “related posts” and removed on ad from sidebar, removed new items from footer 2 (replaced with subscribe), removed images from sidebar for new stories …
home page comes up in 6-9 seconds, vs 1-3 for the other site.
Crazy. Same server. Same php memory. Same mod_pagespeed settings.
And the 1.7 site is loading the gravatars locally, too … still hideously slow.
Hi am,
After what Chris suggested about increasing the memory allocation, upload file etc, in the .ini file. I came across this article which helped me understand the issue:
http://stackoverflow.com/questions/3958615/import-file-size-limit-in-phpmyadmin
Fyi – here are my current settings, and after the increasing the values, demo took split of second to install-:)
memory_limit=128M
post_max_size=128M
upload_max_filesize=90M
Hi guys,
as redtaileagle I have the same problem. Local environment is a fresh made VM (vmware) with Ubuntu 14.04.02 LTS.
php.ini
...
upload_max_filesize = 24M
...
memory_limit = 256M
...
Strange thing is that I did a VM a couple of days ago, same OS, same php.ini & other settings. Everything worked flawless, so I played around the demo and messed up everything as a baby with a new game. This morning I create an identical VM and installed flawlessy WP and the NewsMag theme. Then I tried to download the demo’s data but it freezes just at the end. It downloads something but not all, in fact on the main page you can see texts and can’t see images but if you click on a post everything seems working fine, at least texts and images are ok.
Any idea? because I really can’t understand what’s wrong.
Thank you in advance,
AM
Hi,
@aleister Did you tried Newsmag 1.7 also with latest version of Visual Composer plugin(4.4.3) and doesn’t work? I know that you have that problem with memory, but you can try it just to see if works and also you can change the memory limit. We did not tested latest theme update with older versions of the plugin, but normally it should work.
Also please make sure that you try this only with Visual Composer active, disable all other plugins, clear cache and purge you files if you use CDN. Let me know hoe it goes!
Thanks!
