Messages posted by: jaric

This is late, but: thanks for the info!

Is it possible to change editor from FCKEditor to TinyMCE in InfoGlue? Will stuff like adding images and links from IG still work?

Thanks for sharing!

Hi, you seem to be activated now, so I assume you got around that issue somehow. Welcome!

Thanks!

I found my old code when knowing what to look for and I had implemented it like this:
Is this unnecessary complicated? Especially the part where I check Slot.isInherit()?

How do I determine in a component whether it currently is displayed

* in the page where it was added
or
* in a child page that inherits it since it has no component added in that slot?

I remember writing some code to do this, but I can not find it now and I was never sure I did it the right way, anyway.

I moved to thread to the Core Developer forum. I hope that was OK...

OK, I see. Thanks!

InfoGlue is full of hidden features, that's for sure.

bogeblad wrote:I would say we ditch the template editor.

Excuse a newbie, but: what template editor?!!?

Very good effort, Astik!

Thanks for moving the community forwards

bogeblad wrote:Perhaps we should move this discussion to another thread? Peter J - can you set up a new area for build / tools - discussions?

I suggest you start a new thread in the subforum "Developers/Core Development", named something like "What build tools should we use in the new InfoGlue" (or whatever

).

I edited the last 3 or 4 messages, btw. BB Code was off and that made all quotes ugly. I hope that was OK.

bogeblad wrote:1. Are you willing to share the role of code/commit approver? I.e. can you accept that code is checked into the main branch of IG without your explicit knowledge?
YES - especially if #2!

Great! Yes, if we switch to git (or something similar) and use a good hosting service, contributions will be very much easier to track and accept.

bogeblad wrote:2. Would you consider moving to git for source control?
YES - in the process actually - any input on which hosting service we should use?

My (somewhat limited) experience is with github, and I like their extremely simple way of branching repositories and merging back changes.

A quick search comes up with at least one alternative though:
gitorious - has a system for requesting merges from downstream and hosts such notables projects as Qt and OpenSUSE.

Both are free for open source projects.

bogeblad wrote:3. How do you see Modul1's role in the community in the future?
No idea.

OK, thanks.

bogeblad wrote:4. Do you run infoglue.org?
Yes - but I probably want others to help depending on my decisions ahead.

Great, at least I like if it is in the hands of the community (even if that is only you

) and not some other entity.

bogeblad wrote:5. Would you consider getting the community work going by allowing some trusted users in as admins on infoglue.org (as the site is sadly outdated)?
No problem - i'll be glad to hand some accounts out.

OK!

Thanks for you answers.

Hi mbe!

If you post some code from your component (and content type), maybe we can diagnose the problem together?

One can also note that the admin manual says this about the Default Page Cache Key:

The default key is: siteNodeId_languageId_contentId_userAgent_queryString

But in the site node cover, one should put $ before every part of the key, for example:
$siteNodeId_$languageId

From the source code:

jaric wrote:It should work to add refresh=true&isRecacheCall=true to the query string of the URL to the site node, and maybe that is enough, but it would be nice to have a button or link that explicitly did this (on the content cover for example).

Seems like isRecacheCall does nothing, but refresh=true works.