Pro 6.0: Error after updating

[Misho]

Hi!

I just updated the latest version of a staging website to Pro 6.0, and an error is visible on the front end:

Warning</b> : Dynamic Content return value not scalar : NULL in **/home/customer/www/staging7.optika-kobacic.hr/public_html/wp-content/themes/pro/cornerstone/includes/classes/Services/DynamicContent.php** on line **252**

This is the page:

Dioptrijske naočale - Optika Kobačić

This is the same page with Pro 5:

Dioptrijske naočale - Optika Kobačić

Log-in credentials in the secure note.

Thank you!

[christian]

Hey @Misho,

Thanks for reporting. It would be great if you could keep your staging site online maybe our development team could get in once they view this case.

I believe that in the live site, you already know that warning and error messages should be disabled like the example WP debug setup.

[ZEBRADOG]

Just to add to this, I also had this issue come up when I upgraded from RC1 to the official V6. Luckily I had a backup of the site and reverting back fixed it.

[christian]

Thank you for your feedback. I have posted this in our issue tracker so it’s now in queue to be investigated.

[Misho]

@christian

I believe that in the live site, you already know that warning and error messages should be disabled like the example WP debug setup.

Hi! just to note that WP_DEBUG was already set to false and also disabling displaying errors is not effective on the website.

Thank you!

Edit: Updating to 6.0.1 seems to have the issue fixed.

[Misho]

Perhaps I can continue in this tread. Here is an archive that lost its template after updating:

Ray-Ban Archives

This is the original page: https://www.optika-kobacic.hr/katalog/brendovi/ray-ban/.

Credentials are still the same.

Thank you!

[christian]

Hey @Misho,

I have replicated the issue in my test site so I’ll post this in our issue tracker to be investigated by our development team. We are not sure yet if WooCommerce has a role in this issue.

Thanks for reporting.

[charlie]

This issue will be fixed in 6.0.2 Misho. Product Taxonomy archives were being labeled as singles internally.

[Misho]

Amazing, thanks!

Working now as expected!

[Misho]

…but updating another site to 6.0.2 triggered the same error. I’m sharing this one in the secure note.

[christian]

Thanks for the update, @Misho. I’ll update my report that the issue is still happening.

[charlie]

@Misho are you referring to the first Warning about dynamic content not being scalar? Is there an element that is broken or is it just the warning that you are reporting?

This is a new warning I created to try and identify bad dynamic content pass throughs (Parts of the app were trying to convert a WP_Post to a string even though it’s a class). For the most part it can be ignored unless something is broken.

Thanks a bunch happy new year!

[Misho]

Hi @charlie!

Happy new year!

Sorry for not being clear. I am referring to the broken layout.

But this is strange. Today I re-cheked the layout and it is now not broken. I did clear the cache immediately after making the update to 6.0.2, but it seems that layouts stay broken for a while.

When I say “Broken Layout”, I mean that a default one with the sidebar is being loaded, instead of the one assigned to the Post type or taxonomy.

Thanks!

[charlie]

Okay great to hear. Did you ever save any document in between the time it was fixed and broken? Sounds similar to something else I read so I think that might help me figure out if we need to fix something.

[Misho]

Hi!

No, I just updated the staging copy and left it as is. I just cleared the Supercasher cache, but I didn’t clear the browser cache or cookies at the time, if that helps.

Thanks!