I’ve also confirmed this with different browsers, Chrome and Safari.

Hi Calin,
You said:

…if you rebuild your website only with cloud templates then you can deactivate the standard package, then you should be able to see an improvement…

This is precisely the problem we are talking about here. We have to rebuild our sites to get the speed improvements from v10.

There should have been a automated way to migrate from using the v9 templates and the standard pack plugin to using the new v10 cloud templates designed into the upgrade process.

The burden of moving away from the slow v9 code has been transferred onto your customers. It would have been better if the slow code from v9 was fixed instead of being shoved into a plugin and forgotten.

TagDiv has posted the migration process in this blog post for those interested to read it. It clearly shows the elements affected and describes the labor intensive process to migrate from a site that relies on the standard pack.

So when I updated my clients to v10 and activated the Standard Pack plugin, I did not notice anything beneficial about the update. The site still sucking down extra CPU cycles via AJAX commands, many of which seem to be some interaction with Advanced Ads (which can be CPU heavy in itself). CPU is the single largest expense per month for my clients. And before they had a ssytem that could handle the CPU load of Newspaper, was the single largest point of failure during high load periods. Constant 404 and 503 errors and very slow page performance when there wasn’t an error (I’m talking 13-20 second load times for a page that loads in 3.5 seconds normally)

And yes I know that TagDiv has no control over Advanced Ads, but that plugin does not exhibit this behavior with other simpler “builder themes. I can’t pin the issue on TagDiv, but I can say that there is an interaction between the theme and the plugin that negatively affects server performance.

I know that some people wondered how I was getting along with my site redesign… I decided to use a “builder” theme and a different page builder (which I purchased out of my funds without charging my client for it). It’s not 100% yet and it’s taking more time than I initially thought it would. I keep finding little bits of Newspaper code is still lingering.

So here’s my advice, the only reasons I can think of for upgrading to 10 are:
• a critical security fix
(if this exists, TagDiv has not publicly released the vulnerability)
• a WP upgrade that breaks Newspaper 9, which is a likely at some point.

If either of those events occur, then you my recommendation would be to rebuild your site. If you stick with Newspaper at that point or not is a decision for each site owner/developer to answer. Also, always test on a staging site, never live.

My clients just want a little peace and quiet for a while. I know they’d like to have faster, slimmer sites. But for now, they had to go with a high end, reliably fast hosting provider. Do they want an even faster site that uses less CPU, sure, but that requires them to pay me to rebuild/re-develop their site and comes with all of the risks of new problems. (CPU costs alone are $300 – $500 USD/month for one of my clients)

And to be clear, THAT is my biggest disappointment here. TagDiv took code that they appear to have stopped development on and stuck it into a plugin that v9 sites must use if they upgrade.

Evidence that the Standard Pack plugin is ONLY required for compatibility with v9 sites that use the TagDiv page builder
AND
the same problems that existed in v9 are present in v10 with the Standard Pack
AND
the Standard Pack hasn’t been upgraded since it was released.

That’s just not a business practice that I can recommend or support in any way. I don’t think they are evil, I just think they got in over their heads with their code and are trying to find a way out. But in the process they are doing a disservice to their clients that bought into their page builder.

Lesson learned: Do not rely on your theme builder to supply a page builder and custom code. Just get the best dang page builder you can find and then choose a theme that it works well with and doesn’t try to get too fancy. There are a number of other coders out there who supply good plugins that do what the Standard Pack does who will continue to support their work.

I guess if you’re looking for a ready made solution you can just switch out colors and images, then a theme like Newspaper is fine.

I have moved on.

Hi Calin, I am also seeing these errors in the log files related to td-composer, I don’t know if this will help your developers or not.

With this many issues and bugs to fix, it sure would help those of us who have unhappy clients to give us some idea of when the update will ship. We can’t just keep telling out clients “we have no iea how long your website functionality will be broken” That’s just unprofessional on our part and it’s not nice to put us in this position. Even a vague idea of 1-2 weeks would at least give us a time frame. Obviously, with dev work, a new bug could pop up making the schedule lag, but there is always a schedule of some sort. So we know that even if you give us a date, that date could slip for any number of reasons.

But if I cannot give my client at least an idea of a fix, then they will require me to move away from your theme, and I will have to comply.

You can see what position this puts us in can’t you?

Here is the error code:
Type Error

#0 /www/wp-content/plugins/td-standard-pack/Newspaper/parts/single/loop-single-5.php(57): td_module_single_base->get_item_scope_meta()
#1 /www/wp-content/plugins/td-standard-pack/Newspaper/parts/single/single_template_5.php(28): require_once('/www/wp-content...')
#2 /www/wp-includes/template-loader.php(98): include('/www/wp-content...')
#3 /www/wp-blog-header.php(19): require_once('/www/wp-include...')
#4 /www/index.php(17): require('/www/wp-blog-he...')
#5 {main}

Hi Calin,

1) Thanks for the reply! Can you address the release date for the update?

2) Will the update address the lack of scripts running? No shortcodes or scripts are running on the preview page until the post is published or scheduled is the original problem I posted about with the responsive breaks also a problem.

2) For the responsive break problem, that’s not the case here. We have a side bar, as is evidenced by the space to the right in the first two and the post has our default side bar. You can go to any post on our site and see the problem.
Please see the post settings here: https://imgur.com/AIQIrjO

The page I sent you was for illustration purposes only, but was accurate to the overall problem. We do make the sidebar go away on mobile, but why can’t we adjust the break points for image centering?

And the sidebar widget is empty because that’s part of the bug I originally posted, no sidebars, no shortcodes, no scripts running in preview.

Thanks,
Kim

Hi Calin,
I’d be happy to provide some more info and screen shots of the issue.

For the break points, at 750px or 752px any images on the page immediately are centered in the content area of the post. This is not the same behavior in the previous version and I can’t find anywhere we can control the break points. This behavior makes our site on tablets sort of strange looking, like we picked the wrong image size.

I have examples here with explanations:
https://www.rvtravel.com/test-page-for-tagdiv/
password is newspaper

When is the next update scheduled?

• Can we expect it within a week?
• Two weeks?
• More than two weeks?
• Several months?

My client would like to know how long they will have to use these make shift methods to publish their website?

Thanks,
Kim

• This reply was modified 6 years by imkimc. Reason: changed ol to ul

Hi Calin,

Thank you, I saw that advice to another poster and that was already set to OFF for our website, but still we have the problems. I was able to get images to show up by disabling another plugin for lazy loading. It looks like you’re plugin is stopping any code from running while the post is still in draft form, but once it has been published everything appears OK.

I’ve also noticed some new break points for mobile and those are a little crazy, is there any place we can edit break points for the theme? Do we need to write our own custom CSS for that?

Thank You,
Kim

Thanks for the reply – This seems like important information to distribute when you’re upgrade procedure states that we should delete the theme and plugin files from the website and then install the new version. Just a note on the fact that you will loose all of your sidebars and widgets will be inactive.

Since it’s an issue with WP, it’s not your problem to solve, but it would have been appreciated.

Time to look for a way to export sidebars/widgets setup before a theme upgrade!

Best,
Kim

Hi Vlad,

Of course I already did all of that, with my test site. BUT – I did find that once I deleted all of the theme files and plugins, then re-downloaded the theme to the site and re-installed all of the theme plugins, AND, deleted my local cache, the problem went away. Whew…

I had this same problem, and it pointed to the Composer, but it was actually a conflict with the Clearfy plugin when you choose to optimize HTML and turn off xml-rpc. I do not know why xml-rpc is needed for previewing URLs but that’s what I found out. Hope that helps.

Hi Vlad, I don’t what you just said is true. At least it’s not universally true. We have designed our site using the version 9 and TagDiv Composer. So even if we load the Default Pro demo design in, if we deactivate the Standard Plugin, all we see are the shortcodes on the screen. How do we go about updating the site so that we can take advantage of the new speed functions of Newspaper X?

Will we have to redesign the site all over again?

Thanks,
Kim

• This reply was modified 6 years by imkimc.

You’ll probably have to do minimize and combine your css to unblock the page rendering… I’ve used Fast Velocity Minify and WP-Rocket Cache to accomplish this. There are many alternatives (such as Clearfy which does many other things).

And we have a winner!
I am getting a warning about also including -moz-transform and other browsers, I assume that since the issue only occurs in Safari that this is the only browser we need to apply it to here…
See screen cap of warning here: http://j.mp/2XNsHCS

Entered CSS,
Cleared all Caches,
Purged OpCache,
Regenerated critical CSS (RocketCache)
Still dropdown menu appears under content elements on the page.
Please see screen cap from Safari Dev Tools here:
http://j.mp/2RkhIPa
This shows the error, the html sent to Safari and the CSS codes applicable to the menu when it’s dropped down.
(Note this is a problem ONLY in Safari, have not tried any other webkit browsers)

Thanks,
Kim

Also, you can visit https://www.rvtravel.com using Safari and see the problem when you hover over the category menu…

It’s not what it was originally designed to do, but Advanced Ads might be able to do that with a rotating ad group. You can make the change random or you can weight different “ads”. The groups can be placed with a shortcode.

Anyway, maybe it will work for you.
Kim

That seems to have fixed it,
Thanks.
Maybe the theme needs some tweaking of it’s breakpoints and image sizes? I found several more errors like this one as I was trying to solve the problem with different blocks. Maybe a block editor? It can’t be that hard to edit blocks can it?

Got it, thanks.

Hello @khen888,
I too liked the modal login, but I found that the code updates were prodigious.
I ended up with a small free plugin as well called “Login Logout Menu”. It adds a modal login option that shows up as a custom menu option when you are editing your menus. Then, I made a new menu called “Top Bar Header Menu” and assigned the login/logout menu items to that. It works well.

Best,
Kim
I also use a plugin called “Frontend Reset Password” to customize my lost password page. In that plugin, there is an option to replace the login page with a custom page you build.

Thanks Catalin, the FB page had restrictions but now it works!
Please check out the YouTube instructions in the theme, they are not correct.

Best,
Kim

I did check the system, and I finally found my error in the modification of the plugin. So now it works!
I did notice that you still have to use column text or text with title to get the ShortCodes to both render and still be editable. When I tried HTML code or another of the element types, all I got back was a simple echo of the shortcode.
It would be nice if this was included in an update and that you added an external shortcode element to make it a little easier to use…
Best,
rvtravel.

Hi vickydhumale,

I tried it in responsive design mode on a Macintosh using Firefox and it seemed normal to me. Could it be a caching issue? Have you tried using responsive design mode on a desktop or laptop with the debugger window open?
Do you have “define(‘WP_DEBUG’, true);” set in your wp-config file so you can see if your site is generating errors on mobile?

Best Regards,
Kim

I tried to install the plugin again, and very carefully checked all of the text entries. I am still getting a white screen when I click on the tagdiv composer button when editing a page…

I’m running Advanced Ads, bbPress, Paid Memberships Pro and WooCommerce along with a few other plugins for functionality or utility.

Best,
Kim

Good to know, but in my case, no Rocket Loader. I’m not even caching the site yet (I use WP Fastest Cache). The tagdiv composer works fine until I edit the plugin then it stops working.

pavel since you got it to work, I will try again and see if I can get it to work properly. Big fingers = possible typing mistakes.

catalin, updates soon? Then I’ll know if it’s my editor or my typing causing the problem. (I use BBEdit on the Mac)

Best,
Kim

• This reply was modified 7 years by imkimc.
• This reply was modified 7 years by imkimc.

I applied the changes, and now when I go into tagdiv composer I get the white screen… I’m going to go back and check but I’m pretty sure there were no typos…