I’ve hosted my WordPress site in AWS EC2 t2.micro instance. I’m experiencing difficulties when I try to use tagDiv composer. When I tried to edit and save header value for Mobile view the whole composer becomes unresponsive. When checked the AWS Metrics meantime, it was found that the CPU Utilisation has reached 100%. I need to restart the instance each time. Still I couldn’t edit the header value. What would be the reason?
Disappointed support from team, meanwhile I reinstalled the whole WordPress and retried in a new EC2 instance still the issue persists. I’m initiating a refund request in Themeforest.
Hello !
Please make sure that you have accomplished all the system requirements as in our documentation here: https://forum.tagdiv.com/requirements-for-newspaper/
Please make sure that you do not have a plugin conflict, please deactivate ALL plugins except tagDiv ones, also if you are using child theme or cache plugin, deactivate them, clear all cache and try again.
Please note that at the moment the Support team is not 24/7 available. Please note that we answer the topics from Latest to Newest Monday – Friday from 08:00AM to 05:00PM GMT+2
Thank you !
Before removing Newspaper theme, I’ve tried a completed reinstall of WordPress and used a new instance for the same. I’ve followed https://forum.tagdiv.com/requirements-for-newspaper/ as well before installing the theme. So this completely bare-bone installation with no extra plugins attached also experienced the same issue.
What I concluded from the behaviour is, too much load is pushed back to WordPress host when a slight change is made. So for example when I try to edit the header, for each keystroke a lot of things are happening behind.
An suggestion from my side is to have a button to disable this live reload and only the UI should be rendered when save button is pressed. Don’t know whether this option is already there or is this the exact reason behind.
Regarding the support, I’ve noticed the time frame already before starting this thread. What I noticed is replies where given to another posts which came past this post. So, there might moderators need some time to get back for particluar issues that’s acceptable if a reply is posted like “We’ll get back to you soon” in the thread meanwhile.
Anyhow I’m moving from this theme due to CPU bottleneck I experienced but it’s a wonderful theme. Thanks, appreciate your time. 🙂
Hi,
The thing is that when you you use tagDiv Composer this will make an history so you can use undo -> https://tagdiv.com/embrace-the-undo-and-redo-buttons/ this can be one of the reason that the theme make a lot of request.
I think that this topic it can help you to make the resource from server to be less consumed – https://forum.tagdiv.com/topic/a-few-tips-for-newspaper-x-speed-high-cpu-usage-issues/
Thank you for your understanding and sorry for the inconvenience!
Hi, sorry if I intrude on this topic, but I’m having the same problem on two sites!
Plugin removed or not there is a CPU overload: Only if I disable tagDiv Cloud Library everything returns to “normal”. Moral I have a completely excluded site because I can’t finish building and one that keeps crashing and both block activities on the server. I find no comfort in your answers and I am very worried that I am unable to recover.
For three years I have installed your theme on one of the sites, but only with this version do I have all these problems.
Can you give a solution that can solve the problem?
Thanks
Hi Margherita,
Usually these problems appear when you are not using a dedicate server -> https://i.imgur.com/KzJPSSh.png -> https://forum.tagdiv.com/requirements-for-newspaper/ if you want you canmake a test, try on localhost and see if the problem persists.
Also you can try the suggestions mentioned in above replay.
Let me know the results!
Thank you!
Hi Calin,
Thank you for your answer.
But therefore it will not be a topic for everyone if a server with dedicated services is needed to manage it.
The server configuration is as follows:
CLOUDLINUX POWER LEVEL
PROCESSOR: 2vCPU
RAM (MByte): 2048
PROCESSES: 40
I / O (KB / s): 2048
Unfortunately I can’t do a local test now and the situation is really compromised by the slowness.
Do I need the same requirements if I downgrade to the older version (10.3.2) to fix the situation temporarily? Does something break in the theme?
Thank you
Margherita
Hi,
These requirements were since Newspaper v9.8, the only major changes in Newspaper X was to separate the standard element from cloud element. If you want you can downgrade the version, but first make sure that you made a full backup to your website and database.
Thank you!
