Home User profile
tagDiv Member
This user did not write anything. So we are just showing here some random text to make the profile page look nice :)
jamie@gundigest.com
tagDiv Member

Hey Calin,

Yes, a developer modified functions.php of the parent theme and that was the issue. All modifications have been moved to the child theme and the child theme functions. Thank you for your help.

jamie@gundigest.com
tagDiv Member

Hi Calin,

Thank you for your response. The error did not resolve after following your suggestions. These are the steps I took.

– I verified I am using the latest Newspaper theme 12.7.1.
– I removed the child theme folder from wp-content/themes
– I refreshed the themes page in wp-admin to verify the theme was gone.
– I created Newspaper-child.zip from the theme package.
– I installed Newspaper-child.zip by uploading it into the WordPress admin panel. – WordPress said the installation was successful.
– I went back to the themes page and tried to preview the child theme.
– The same error showed.

2025/08/08 21:18:37 [error] 118#118: *1710 FastCGI sent in stderr: "PHP message: PHP Warning: require_once(/www/kinsta/public/mysite/wp-content/themes/Newspaper-child/blocks/acf-blocks-loader.php): Failed to open stream: No such file or directory in /www/kinsta/public/mysite/wp-content/themes/Newspaper/functions.php on line 644;

It is still looking for the /blocks/ folder in the child theme:

PHP message: PHP Fatal error: Uncaught Error: Failed opening required '/www/kinsta/public/mysite/wp-content/themes/Newspaper-child/blocks/acf-blocks-loader.php' (include_path='.:/usr/share/php') in /www/kinsta/public/mysite/wp-content/themes/Newspaper/functions.php:644

Thank you for any help you can provide.

jamie@gundigest.com
tagDiv Member

Hello Bettina,

Our pages are not default or built with another builder.

It is extremely frustrating that we are asking for help from TagDiv support and you are responding with cut and paste replies from other support threads, and that now you are saying that we need to completely redesign our website.

We have read all the other threads on this topic and in some of them you ask for login credentials for the site so your team can take a look. Are you no longer providing this type of support?

We have only ever used tagDiv Newspaper as our theme, so we don’t think it’s unreasonable to ask for help when your latest version is not displaying our site correctly and there seems to be no way to repair it. We paid to update our account to give access to support, but we don’t feel like you’ve provided much support thus far.

Please let us know what kind of actual support is available outside of links to other threads and suggesting that we completely redesign our site of 7000+ posts.

Thank you,

jamie@gundigest.com
tagDiv Member

Hi Bettina,

I have followed all the steps you mentioned in the post you linked and they did not resolve the issue.

Suggesting that we try on a fresh WordPress install does not help with the issue we are having. We do not want to rebuild the entire site. We are simply attempting to upgrade from Newspaper 9 to Newspaper 12 in order to take advantage of the malware patch in Composer version 4. When we upgrade, the site looks fine except that the header with our logo and menu no longer shows. And with Composer throwing this error we cannot edit the page to fix it.

The “Error at zones: 6(models) : 5(dom). The model does not match the content Current state has involved an issue.” error does not appear when editing using Composer in our Newspaper 9 site, but only after upgrading to Newspaper 12.

We have also tried updating to Composer 4 on our Newspaper 9 site, but installing it creates a critical error.

Can you give us any more assistance to get this resolved? Please help.

Thank you,

jamie@gundigest.com
tagDiv Member

Hi Bettina,

The screenshots you’ve posted don’t seem to be relevant to our question. They only talk about why Newspaper switched from WP Bakery to Composer, and why we should recreate our pages in Composer.

We would love to recreate our pages in Composer, but the error is thrown on every page, even when creating a new one. See this screenshot from composer when trying to create a new page. https://gundigeststg.wpengine.com/wp-content/uploads/composer-error.png

Composer doesn’t function while this error is present – no elements can be added at all.

How do we resolve this error so that we can create new pages or edit with composer?

Also, you didn’t address the main issue, which is the header not showing on one of our sites after the update, but showing on the other. What would cause the header to not show or be available? Please look at the production (Newspaper9) and Staging (Newspaper12) links I posted for each site to see what I mean.

Am I correct in assuming that we need to have Composer functioning correctly (ie resolve the error) to edit the header? Is editing the header in Composer the only way to resolve the issue we are experiencing?

Thank you,

Viewing 5 posts - 1 through 5 (of 5 total)