Article caching issue

I'm new to Infoglue, but I'm very impressed with the functionality it provides.

I have a hierarchy of templates that are used to build up pages. Each page created using these templates will render an article. The problem I'm having is that there seems to be a caching issue as when I access the fist page the page and the article load correctly, accessing any other page loads exactly the same content. If I clear down the cache and then access the pages in a different order the article on the first page accessed always shows.

For example:
1. Clear cache, access About Us page (shows correctly), access Help page (shows About Us article), access Legal page (shows About Us article)
2. Clear cache, access Help page (shows correctly), access About Us page (shows Help article), access Legal page (shows Help article)
etc etc

I know this functionality should work because it is very similar (if not the same as) the www.officestand2.com demo that comes with InfoGlue.

Please can someone point me in the right direction to help solve this issue.

Thanks,

Mark.

Hi Mark,

I haven't seen that issue, but maybe we can try to find out what's happening. The obvious question is of course whether you have changed the cache settings in any way?

Other than that, have you been developing your own components, or are you using the stock components?

On each page, have you bound an article to each article component present on the page? Otherwise maybe some kind of crazy cache inheritance behavior may be active.

Would it be possible for you to post some screen shots of for example the page structure (right click in the page and choose "Page Structure") on one of the problematic pages, and your cache settings in "Management Tool->Application Settings->Edit Properties->Cache Settings"?

I found the solution to my problem, I had to turn off the use of inheritence when loading the articles in my JSP code. I'm using a mix of JSP and Velocity, although I'd prefer to use just JSP I can't seem to work out how to do everything that I need to do in it, so I'm having to use Velocity.

arcotc wrote:I found the solution to my problem, I had to turn off the use of inheritence when loading the articles in my JSP code.

Great!

arcotc wrote:I'm using a mix of JSP and Velocity, although I'd prefer to use just JSP I can't seem to work out how to do everything that I need to do in it, so I'm having to use Velocity.

My experience is that JSP can do everything in an ordinary component and we haven't needed to use Velocity at all (except for in our CSS components, since our graphics designer prefers Velocity there). If you'd like to, you can post an example of where you have to resort to Velocity and maybe we can see how it could be done in JSP?

Jaric,

I'm absolutely convinced that you're right about being able to do everything in JSP that can be done in Velocity, my problem is finding out how to do these things. I've been written Java code since JDK1.0.2, and making a living out of it, so I should be able to do it (which is frustrating me).

Can you point me in the direction of any resources (outside of the Developer Guide - which I've found useful in many cases but not all)?

Thanks for the offer of support, I might just take you up on it (when I get back to this project).

Mark.

arcotc wrote:Jaric,

I'm absolutely convinced that you're right about being able to do everything in JSP that can be done in Velocity, my problem is finding out how to do these things. I've been written Java code since JDK1.0.2, and making a living out of it, so I should be able to do it (which is frustrating me).

Can you point me in the direction of any resources (outside of the Developer Guide - which I've found useful in many cases but not all)?

I've been diving into the source code quite much and Google has been my friend of course. I also have had the fortune to be able to ask the InfoGlue core developers questions now and then. I am sorry I can not provide a better answer than that..

Thanks for the offer of support, I might just take you up on it (when I get back to this project).

Please do!