FYI; you don’t over write when uploading via FTP; as you end up merging old and new copies.
Via ftp you need to *delete* the old newsmag folder, and old td-composer plugin; then upload fresh copies from scratch; then login, then activate the td-composer plugin.
That’s how I do it without any issues 🙂
What php version are you using?
Did you try installing clean copies via FTP, deleting the ones you previously installed?
Disable all caching prior to install?
(I don’t work here, just looooong time user.)
Isn’t this done in the wordpress > admin > menus section ?
I’ve been building websites since 1995 and FTP has *always* been the best way to update themes due to various localized file permissions, folder ownerships, how WordPress was installed (eg., WP can behave differently if installed via Plesk panel, etc.); time outs on your system during updates causing missing file, unzip issues at server level, mix of old/new files in some cases if server/domain/site/wp does not first properly remove the old files prior to install new ones; caching issues (are you disabling cache prior to updating?) causing mixed content; conflicting plugins, etc.
Just giving some friendly advice from an elder webdev who has “seen it all” over the years and we run in paranoia mode over here.
Good luck! (I don’t work here; but have used Tagdiv products since they launched). Not meaning any insult or anything, just some friendly feedback.
Best way to do theme update is to always do so via FTP using un-zipped files; first on server deleting the td-composer plugin folder, and the theme folder; then uploading fresh copies, then going into the plugin manager in WP admin, and activate td composer. This is how we do it without any issues; running latest WP and PHP 8.3x. And, always make backups so you can roll back if you mess something up.
We are getting no security warnings in the latest release of Newsmag on PHP 8.3x.
To O.P. — good to look at general best practices for security for any modern website, wordpress install, etc.
————–
YOUR SITE:
Hardening Improvements
Security Headers
Missing security header for ClickJacking Protection. Alternatively, you can use Content-Security-Policy: frame-ancestors ‘none’.
Missing security header to prevent Content Type sniffing.
Missing Strict-Transport-Security security header.
Missing Content-Security-Policy directive. We recommend to add the following CSP directives (you can use default-src if all values are the same): script-src, object-src, base-uri, frame-src
Leaked PHP version. Your site is displaying your PHP version in the HTTP headers. Please set expose_php = Off.
I would not go over PHP 8.3 personally.
Also, fyi; Google etc. is smart enough to know difference between H1 on an image as logo and H1 for the primary title of page which would also be in the META data. Technically HTML5+ supports multiple H1 tags, just like multiple H2 tags. Bots can line page canonical, meta and primary textual element on page to determine the “headline element” of a page or post.
It is common practice to make the logo an H1.
Just some random feedback. 🙂
I have been going to our page and manually posting the headline then pasting in the story link. Annoying, but that still works. 🙂
I had this happen once because the ‘author’ was not actually given contributor or editor rights in the user settings, so could not actually be a real author although that author name selected on the post edit page. Probably not the same issue, but check the user setting for that author to make sure higher than subscriber. 🙂
we use formidable forms now
Yes. Having same issues here. FB pop up just “spins” and never fully instantiates.
Lots of weirdness; just tried sharing a story on AI to one of my FB business pages, using the FB button on USATODAY, and got this:
User opted out of platform
The action attempted is disallowed, because the user has opted out of Facebook platform.
Return home
Then went to CNN, and tried to share story about Disneyland 70th, and also got the blinking share box not loading.
So, not unique to the Tagdiv themes, but hella annoying.
We are having this issue on our sites with FB using latest Chrome the past week or two. I think it might be related to a common WP plugin many use, but have not debugged that yet. Will update if I figure it out.
Works for me on multiple sites. Generally Newsmag has *always* worked with every new iteration of WordPress core.
For some odd reason Themeforest didn’t seem to send out a note about the update. I didn’t get one, and generally always have over the years.
Works fine with latest WP. However, I’d stick with PHP 8.2x.
are you clicking [save] after you uncheck (toggle off) the display options?
under theme panel > social networks > first ‘tab’ at top > social share 🙂
I am using this temporarily, but latest version has security issue if using [shortcode], pending updated version in WP repo:
https://wordpress.org/plugins/scriptless-social-sharing/
I usually update via FTP;
(make backup of site!!)
a) delete theme folder
b) upload new theme folder (not zip file)
c) delete plugin
d) upload updated plugin via FTP (not zip file)
e) go to plugins and make sure updated plugin enabled.
f) CLEAR CACHE if any.
(I don’t work here.)
if the plugin injected code, their support should tell you how to remove?
What did the seedpod plugin folks say about cleaning up their code?
Sadly, Google’s ad platform is crap. They do all the stuff they once penalized sites for, like moving content below the fold, slowing down page, causing page to move around, and poor time to load.
Not sure if tagdiv emables any of this, or plugin needed,
ref
https://developers.google.com/interactive-media-ads/docs/sdks/html5/client-side/preload
(I don’t work here.)
fyi, you can use Chrome Console ([F12] on windows) to look at the element, then simply add the new color to the CSS element; I add my custom CSS in the WordPress customizer so it won’t go away with any updates or reinstalls.
(I don’t work here.)
