Main things to watch out for:
– custom CSS in ‘theme’ panel, might be better in customizer; but expect some stuff will need update due to different ‘selectors’
– probably have to rebuild home page in theme builder (just like going from newsmag 3 to 5)
– probably need to redo sidebars (make sure to copy/backup any custom stuff into external file to redo)
– may have to redo header and footer
– will likely have to choose new defaults, for post template, archive templates

Not too horrible. But staging site recommended.
One thing I am testing out now is “WP-Staging” plugin which is kinda cool for this kind of thing.

(( disclaimer: I don’t work here just way early adopter years and years ago in the TagDiv multiverse 🙂 ))

We had some weirdness the other day with one of our old sites running Newsmag 3 also; the menus got rearranged oddly – suddenly the top bar was the main nav bar. I reset that easily, but only updates were on the web server itself for PHP 7x and such. This happened prior to the latest WordPress update today.

We’ve got one site migrated to NM5 and PHP 8.1 and minor pain; really just rebuilding home page elements, but code is a little cleaner now. Most of the tricky stuff now in the composer plugin, following the practice of stuff like elementor, etc. — way less file withing file within file and endless redirects like v3 (ahem).

Anyway: this only happened on (1) site; with NM3x (final version), and PHP 7.x. But scanned site for malware and nothing found, so chalking that up to some oddity on server. Not using ‘Visual Composer’ – only TagDiv Composer.

Good time to move to Newsmag v5, frankly.

Advisable, but I didn’t do it: turn debug on in the wp-config file to write error log into content folder; then check it for anything notable beyond deprecation warnings. 🙂

Hi, yes, I think the 681×0 is to auto size the height, since width is necessary to “fit” in say the boxed layout.

If not already set, also check the PHP timeout and PHP memory settings.

I basically have 3 sizes for home page plus slider; and then use one of those in sidebar; and one in sidebar with no images. For posts we use inline image not featured image, so the image we upload *is* the image used in template. Heh, so maybe we have 5 modules. Better than 12 + the 3 from WP default!

Usually good to go into the theme settings and deactivate all image module sizes not actually being used. I try to limit mine to no more than (4) module types to limit this issue. Also, go into the WP default media settings and put 0 in all three items to not have those sizes built.

careful with new youtube share codes that add new tracking id on end…you may need to remove the tracking id for videos to always embed properly

similarly, video shorts require special embed method

i just wrap first sentence in a span, and use style, font size larger

awesome! thanks

Facebook has issues from time to time capturing an caching the open meta data (you can view source your post page to see if the opengraph data is there).

When FB skips image, solution is usually to go back next day to the post on FB, then click the “refresh attachment” option.

That’s what I do anyway 🙂

Internal linking does not need to be “nofollow” — Google bots still follow all the links regardless. What matters is the META data on the tag page itself, which Yoast should override to say “noindex” which is what Google cares about. Meaning, if you have a link to tag page from a story, that links to tag page which is marked noindex and the tag links back to the original story page with canonical link in the meta, you’re fine.

Yoast will also keep the tag pages out of the sitemap, based on the toggle being ‘off’.

This has been our experience anyway. (I started doing SEO in 1995, if that matters.) 🙂

Probably need to specify what issue you are having so the support team can assist (I don’t work here).

I usually do the sidebar at top of the two column grid.

[ slider xxxxx] [sidebar]
[ second feature]
[ col a][col b ]

• This reply was modified 2 years by simchris.

FINAL SOLUTION: Make sure you upgrade site to WordPress 6.4.1 — the version 6.4 had four major bugs, one of which broke all cURL functions. WP 6.4 should not be used by anybody.

[*RESOLVED*]

Make sure you upgrade site to WordPress 6.4.1 — the version 6.4 had four major bugs, one of which broke all cURL functions. WP 6.4 should not be used by anybody.

Better solution if getting cURL bug breaking things:
This appears to be the temporary fix:
https://github.com/WordPress/Requests/issues/838
download the zip to replace:
To fix the issue, replace /wp-includes/Requests/src/Transport/Curl.php with the following file: Curl.php.zip or see #838 (comment)

Note, if you’re having the cURL bug in WP 6.4, you can rollback to 6.3.2 using plugins that do that; or you can replace a core file
To fix the issue, replace /wp-includes/Requests/src/Transport/Curl.php with the following file: Curl.php.zip or see #838 (comment)
https://github.com/WordPress/Requests/issues/838

Note: if you just installed WP 6.4 and ran into issues (in our case it broke the cURL function to Apple News); you can ‘roll back’ to WP 6.3.2

We used the plugin: ‘WP Downgrade | Specific Core Version’

Note: if you just installed WP 6.4 and ran into issues (in our case it broke the cURL function to Apple News); you can ‘roll back’ to WP 6.3.2

We used the plugin: ‘WP Downgrade | Specific Core Version’

Oops. Sorry. My post was on wrong topic. Ignore.

• This reply was modified 2 years by simchris.
• This reply was modified 2 years by simchris.

What is your PHP memory limit set to?

You may need to install an SMTP plugin to send out emails properly from your domain/server. This is common issue with WordPress. Often ‘sendmail’ via PHP does not send emails out, or they are seen as spam by receiving person, so never received.

(I don’t work here.)

Best practices for favicon is to simply make the various sizes for different browsers and FTP them into the root of your domain, where the WordPress index file lives. This is then independent of any theme, or theme setting.

usually this happens when you don’t ‘re-enable’ the composer plugin after updating everything. I had this happen recently with newsmag.

Might not be your issue, but double check the composer plugin updated and activated under the plugins section in WordPress. 🙂

(( I don’t work here. ))

Use the above “example” and modify as needed to tweak the elements beyond the base body font size (e.g., 16px or 18px is good size for that).

Just suggestion. (I don’t work here.)