Cannot clear cache on design parse file

(Jlouise) #21

[quote]
hi there -

www.ausdayparramatta.com.au

What do you see

[/quote]

Ok for us here now it is not even picking up the new design it is still picking up an old delted one… argggghghhghhghhgh

(Shane Weddell) #22

[quote]
hi there -

www.ausdayparramatta.com.au

What do you see

[/quote]


    
    
    
    Home | Australia Day Parramatta
     
    
     
     
     
    
    
    
Ahhhhh !!!!
(Shane Weddell) #23

That is source of course.

(Robin Shi) #24

Yes i have seen same Ahhhhh !!!!

(Jlouise) #25

[quote]


<p>Ahhhhh !!!</p>



[/quote]

Yeah this is how we feel…

When we drop all the customisations, it works, if we try to start adding customisations it does not pick them up… as if it is not parsing the file…

Also as soon as we paste a design area for css the locale manager error comes up…

(Shane Weddell) #26

Have you just had an upgrade? Seems like your issues are in the Locale file and there has been issues that have been missed in the upgrade.

(Jlouise) #27

[quote]
Have you just had an upgrade? Seems like your issues are in the Locale file and there has been issues that have been missed in the upgrade.

[/quote]

We are starting to think the same…

(Ryan Callaghan) #28

Can't really give many suggestions cause I cant see the backend,


But some quick tips (sorry if you've done this already)


  1. Link customisation, not the design
  2. Put body tags in matrix (The MySource tag) and make sure the content is under the body tag.
  3. clear squid cache.



    If you can let me know whats going on with those 3 I listed, I'll try help some more :slight_smile:
(Jlouise) #29

Hi - thankyou for helping

  1. Link customisation, not the design - did this
  2. Put body tags in matrix (The MySource tag) and make sure the content is under the body tag.- did this
  3. clear squid cache. - we dont know how…not even sure if we have it…
(Robin Shi) #30

see some change
<div id="content_div_43646">

What's up???



</div>



You are using IIS not Squid

here is the header

Via: 1.1 MSM-ISA

Content-Length: 548

Expires: Thu, 15 Oct 2009 06:46:23 GMT

Date: Thu, 15 Oct 2009 04:46:22 GMT

Content-Type: text/html; charset=iso-8859-1

Server: Apache

Cache-Control: max-age=7200, public

Pragma: cache





200 OK<br><br>I think nothing wrong with proxy or parse file updating since you can add the Matrix body tag. Go through the parse file to see if any mistake. If there is Matrix normally drops off that design area tag.<br>

(Ryan Callaghan) #31

you might, or might not to clear squid cache do the following.


1: At the top of the page next to the search box you have icons, click the 2nd icon "Tools"



2: Just for a little test, clear the matrix cache first.



3: Go back to the Tools page, the 6th option is "Clear Squid Cache" (if you have it), click it will take you into the edit screen



clear your design asset, and your "site" tick clear now. and Commit



Also when you've done this if it doesnt work, check if you've applied the right customisation sometimes its easy to get lost especially with a site that has 3 or more designs in it.

(Ryan Callaghan) #32

http://www.ausdayparramatta.com.au/_recache


^



Try that as well. (if your using a version later then 3.20)





If you want to send me a copy of your pase file, I can have a look at it and see if there is any mistakes in it.

(Jlouise) #33

Hi everyone and thank you thank you for all of your help…
turns out it was human error (oopsie sorry)

ok here goes I owe everyone an explanation…

Turns out that there was syntax error…

This

<MySource_AREA id_name="common_css" design_area="linked_css" >

was meant to be this

<MySource_AREA id_name="common_css" design_area="linked_css" />

Notice the missing slash at the end.

This was causing the locale manager error.

So the parse file was getting to there stating the error then not (of course) parsing the file…

But of course when we were taking this code out the file was being parsed becuase there was no syntax error…

which is why we were getting confused…

THank you to all for all your helpo

And apologies for wasting everyones time…

(Shane Weddell) #34

Either would actually work however there are a number of design areas that will never work from the parent design asset and require a customisation to be created and used. If you had incorrect tags you would also have had issues in the initial parse of the design.

My money is on a bad upgrade or bug. If you have an innocuous design somewhere in your system try a manual re-parse on that and see if it turns up the same locale errors.
(Shane Weddell) #35

Hehe, bugger it. There goes my money :slight_smile:

(Ryan Callaghan) #36

its very very simple to make human errors :P!


If all else fails, read over your parse file!

(Jlouise) #37

[quote]
Hehe, bugger it. There goes my money :slight_smile:

[/quote]

yeah sorry guys

we were so caught up in the non parsing of the file and the locale error that we were overlooking syntax errors… even though we thought we had looked at this over and over we just totally missed it…

was not until we started again and entered back into the design 1 line of code at a time that we saw our error…

again apologies guys…

(Ryan Callaghan) #38

Nothing to apologise for :)!


Glad its all working.

(Shane Weddell) #39

Did the locale error actually give you the tag that had the error?

(Jlouise) #40

[quote]
Did the locale error actually give you the tag that had the error?

[/quote]

hi,

No it didn't, which is why it took us so long to pick it up.

It was only when we entered this line of code and the error showed up… so we took it away and the error went away - that we realised there was something wrong with that line of code.

As soon as we found the syntax error and re entered the correct line of code we never saw the error again…

if it had have given us a heads up we would have found our mistake much sooner…sadly…