# Error Checking problem persists with PG 9 Beta

**URL:** <https://forum.pinegrow.com/t/error-checking-problem-persists-with-pg-9-beta/11287>\
**Category:** Bug Reports\
**Created:** [December 28, 2025, 12:55pm UTC](https://forum.pinegrow.com/t/error-checking-problem-persists-with-pg-9-beta/11287 "2025-12-28T12:55:15Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![schpengle](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/schpengle/32/238_2.png) [@schpengle](https://forum.pinegrow.com/u/schpengle)\
**Post date:** [December 28, 2025, 12:55pm UTC](https://forum.pinegrow.com/t/error-checking-problem-persists-with-pg-9-beta/11287/1 "2025-12-28T12:55:15Z")

</div>

HI, I cant carry on with the previous topic posting:-

> [@Problems with Error Checking AND Pinegrow rendering a HUGO site, both locally and via URL](https://forum.pinegrow.com/t/problems-with-error-checking-and-pinegrow-rendering-a-hugo-site-both-locally-and-via-url/10933):
>
> Hello. Im not sure if I’m doing something wrong but I get this a lot when I use PG. PG V 8.5 Mac. Open URL. PG says there are a pile of errors. Create folder to save locally. Check code, find errors, click button to refresh, check for errors. ALL errors dissapear. including when I havent reallly done a lot. this is the Yellow, box on RIght, number 1. then, follow the advice of dialogue box to go Page\>Check for html errors and Now pops up box number 2 in red on the left and… ShaBaNg! …

as it was closed.

But the problem persists.

so for instance.

On the very first opening of a URL.

PG correctly finds a single fault.  
Divs within a Span - semantic/structural error.

but then if you make ANY change and save it, even to include simply syntax errors, ie, just including a space  
in  
**sp an**

it passes as fine in the pop up error checking, while the code editor blows up with warning symbols.  
they are incongruous and don’t tally, so which one of them is correct?

So the original structural error persists, which was correctly picked up by PG parser, plus one new syntax error, but it all now passes as fine and the original error which WAS initially picked up, no longer is.

which one to believe?  
Code editor or error checking modal pop up window.  
If not the latter then its not much use really is it 🙂  
As that is its actual purpose.

It would be nice if they both reflected each other

 ![Screenshot 2025-12-28 at 12.47.59](https://canada1.discourse-cdn.com/flex036/uploads/pinegrow/original/2X/d/d42ba730c4496031da5e443afd049b983a6e55ed.jpeg)

NOTE!

if i remove the space in **sp an**  
then error check from menu

PG no longer flags the initial error.

_Page_→_check page for html errors_

So why does it pick it up initially, then fail to when **refreshed** but the code is reverted to original, containing only the initial error, which it once flagged up and no longer is able too?

It’s as though its checking some other saved state of the page, or other previously corrected page in the project/its cache or not actually refreshing its error check at all when you click the blue refresh button.

Cheers.

Great on the new PG9 btw and Happy New Year.