Messages posted by: jaric

Do you have anything in the beginning of your page that affects how expressions are treated? Some JSP directive or something?

The stock IG Sitemap component at http://www.infoglue.org/Developers/Components/Component_detail_page/?contentId=539 uses sortPages. Does that one work for you (i.e. do you still have it in your repositories somewhere)? If it does, then you can try to find the difference between your component and that one, otherwise it looks like something broke at some point, I guess.

In the source (for my version, which I think is 2.9.8.2), the input parameter is handled like this:

Which finally boils down to:

To me it looks like that the input should be an expression, ${...something...}, (like you have) that should evaluate to a List. And that would mean that childPages is not a List... Which is bizarre, but who knows? If you use the code below (not tested), what does it say?

With a little insight in what's going on, my guess is that 3.0 will not be ready for use any time in the close future. I will happily hear something else from any of the Modul1 guys, though!

The main developer of InfoGlue, Mattias Bogeblad, has quit Modul1 to work for another company. I do not know if he will carry on working with InfoGlue there or not, but I am sure it will affect the future of IG, and in particular 3.0.

What happens if you, instead of using a property as root for the child pages, instead use a site node? As in the example:

After checking the manual, I must admit I don't think my guess is correct... I see that you've basically followed their example exactly, and yet it fails? Strange.

My immediate thought is that the input parameter isn't supposed to get a List. Maybe it should get the id of a list? That is, removed the ${}. Just a guess.

OK, I see

I guess InfoGlue would need a solution where you can set up mapping rules. For example, http://<host>/profile/<something> could map to http://<host>/userprofile?user=<something>. This is quite common in other web contexts, I think, and would be a good addition to IG. That would make your job much easier.

If you are running Apache I am pretty sure you could use mod_rewrite to to this.

arcotc wrote:I've managed to find an undocumented tag, remoteSiteNodeService, in the structure tld file, but I'm not exactly certain how this works.

Undocumented features are cool! I haven't used it though, but would a solution where the link is something like this instead be OK?
That would be much easier to implement since you then only need to have one static page with a component that retrieves the user name from the URL parameter user.

astik wrote:The problem was encountered on 2.9.7.1 Final (2009-05-10) which is the latest official version.

Actually, if you go via the official site you end up at http://sourceforge.net/projects/infoglue/files/ where the latest stable version is 2.9.9.2 Final.

I solved the above issue. I checked out the InfoGlueInstaller:

There is a new file called upgrade2_9_7_1_to2_9_8_7.sql which contains the following SQL:

Running that in mysql made my reps work again.

I was running some earlier version locally on my development computer and upgraded to the source code to 2.9.9.2 from CVS. The I ran the supplied ant-script (with my previous build.properties) and it seemed to install correctly, but when going to my existing reps in the structure tool I get this error:

I think it looks like they updated the database schemas, but I don't know.

We actually have that method in a helper class called CategoryUtil, which is placed in jar that we deploy to our server. As long as it is located in the lib directory it will be usable from the JSP page.

Put it inside <%! %>. Then call it from inside <% %>. Like this:

Something like that. Not tested at all!

Would you mind posting the relevant part of your component? Where you're using pageUrl, that is?