I had almost the identical issues with you the other day as well.

It as suggested I fresh install them (and plugins) via ftp. That solved most of my problems. I also couldn’t update theme normal way.

So, long story short. And when I say long…

Anyway, turns out. Host was able to fix the problem. Although everything pointed to it being Newspaper issue. An amazing support rep at Rocket figured it out.

Posting here in case anyone ever has a similar issue, so a potential solution may be documented

They I added this on htaccess
Header always set Content-Security-Policy “frame-ancestors ‘self’;”
And that seemed to fix it

The CSP rule was just too strict after the restore. It blocked the page from loading inside the TagDiv Composer’s iframe.
Once the rule was adjusted to allow framing from your own domain, everything clicked back into place.
The server itself was working fine; it was just the browser being told “don’t show this page inside another page.”

Thanks for that tip. It DID work. Got me to 12.7.3
Half the problem was solved. Other half, no such luck.
But. Posting an update below for anyone in the future if they have a similar problem

Thank you!

UPDATE: Sorta…

unable to edit any templates (e.g., post or category templates). When I attempt to open a template for editing, the Composer editor either fails to load, displays a blank screen, or encounters an error, preventing any modifications.

Crucially, the TagDiv Composer seems to work for editing regular pages and posts. I’m guessing the problem is specifically localized to the template editing functionality?

I’ve already done many troubleshooting steps, including:

WordPress & Theme/Composer Versions:
– My WordPress core is up-to-date. 6.8.3
– Dashboard says WP, Themes and Plugins are all up to date. but on the Newspaper updates page it shows I need to update to 12.7.3
– Newspaper theme currently updated to 12.6.9, can’t upto to 12.7.3

Theme Reinstallation Attempts:
– I’ve tried a significant process to ensure theme integrity: I manually downloadeed 12.7.3 from ThemeForest and then performed a fresh, clean update to the current latest version of the Newspaper theme and its associated plugins. This was done to rule out any corrupted files. It wont et me update though, it doesnt complete it.

Site Restore:
– I performed a full site restore from a recent working backup, but the template editing issue persists.

Caching Management:
– I have thoroughly cleared all levels of caching: my WordPress caching plugins (e.g., [mention specific plugin if you use one]), server-side cache via my hosting provider, CDN cache (Cloudflare, etc.), and my browser cache (including incognito mode).

PHP Environment Configuration:
– I have verified my server’s PHP version (currently running 8.3.22)
– I have also manually increased critical PHP limits in my php.ini and wp-config.php, including:
– memory_limit 1024M
– post_max_size 1024M
– upload_max_filesize 1024M
– max_execution_time 600
– max_input_vars 5000

WordPress Core Diagnostics:
– I’ve checked the WordPress Site Health tool, and it reports no issues
– I’ve re-saved permalinks from the WordPress settings.
– I’ve tested editing in different browsers, ccomputers and incognito/private windows.

Plugin Conflicts:
– While pages/posts edit fine, I have also systematically deactivated non-TagDiv plugins that might interact with editors or custom content types to check for conflicts, but the template editing issue remained.

My leading hypothesis is that the problem may be tied to a version mismatch or conflict? My current system is detecting Newspaper Theme 12.6.9, while it seems certain theme components or template assets might have been created or are expecting an environment compatible with Newspaper Theme 12.7.3? This discrepancy appears to specifically affect the way TagDiv Library interacts with or loads template files, as all other Composer functionalities for pages and posts appear to be working correctly.

Could you please provide guidance on this specific issue? I can provide screenshots, access to the browser console, or temporary admin access if needed.

Thank you for your urgent attention to this matter.

• This reply was modified 9 months by mikeshecky.

Wow, sounds like you sure know what you are doing. Way better than I do.

Appreciate all that info, will have to run it through GPT to interpret what it means. Beginner here, but the bottom-line takeaway. Can’t be done, huh? But you gave an indirect method as a workaround?

Awesome, thank you!!!

WOW, I thinkn you fixed it. And it was way easier than I thought it would be.

THANK YOU.

No Child Theme
Cleared caches on multiple levels before going through plugins one by one. Turns out, that’s all it was.

I was convinced there was a way to control how signed in visitors saw the vs. non signed in visitors. And wasted hours trying to find that lol

Thanks again

Apologize for not including images. I thought the description would hopefully lead to answer why signed in users are seeing what appears to be a different template than what non signed in users are seeing.

Here are the images:
– Not signed in user, broken footer
– signed in user, working footer
– http://not signed in user,completely different look to the post (template?)
– Signed in user, post looks correct

All images: https://imgur.com/a/mWhN1wK

Wow, thank you for such a quick and thorough reply!!

Step 1 sounds straightforward enough

Step 2 – I though tI did AMP through Newspaper theme. I checked installed plugins and I see one called “AMP”.
A) How do I determine if I used AMP for WP?
B) I use Rankmath if that changes anything, not Yoast

Any guidance on Step 3 is appreciated – I can write great, I can rank even better. But I am completely illiterate when it comes to the tech side of blogging. SO I appreciate your help and patience!!!

THanks again

I’m having the same issue, not seeing composer option on top