CMS Made Simple Forums

Hello all,

I have set up a CMSMS version 1.1.2 on www.siscon.nl. The cataloger module has been installed to display the assortment of the company.  Everything has gone well, but for the cms selflinks. When I make a selflink on one of the productpages and I then take a look at it in the front-end, the selflink has not been processed and still looks like

{cms_selflink page='documentatie' text='U kunt hier onze documentatie vinden.'}

It only happens when I make a selflink from a catalog item to a normal CMSMS page. Has anyone ever experienced this error? Does anyone know about a solution to the problem?

Siscon.nl is the only site where I use the cataloger module, so I don't have any material to compare.

Thanks already!
Boov

boov wrote: the selflink has not been processed and still looks like

{cms_selflink page='documentatie' text='U kunt hier onze documentatie vinden.'}

You see this in your page?
Check for WYSIWYG replace, maybe TinyMCE replace { } with html entities.
Turn off check of your WYSIWYG

Alby

After turning off my WYSIWYG (FCK) it still won't work.

It seems as if the cataloger module does not know what to do with selflinks. Anybody know a possible solution?

Thank you!

boov wrote:When I make a selflink on one of the productpages and I then take a look at it in the front-end, the selflink has not been processed...

Hello boov!
And everybody else.

5 years later (today) I am running CMSMS version 1.11.2.1 and Cataloger version 0.11.2 and ran into the exact same problem! You or anyone else has a proposed solution?

This is how my un-processed link looks like on test ground:
http://klee.se/adnotam2/%7Bcms_selflink ... ulsson'%7D

This is what it should be:
http://klee.se/adnotam2/index.php/musik ... s-paulsson

I really appreciate the workings of Cataloger - this is the first obstacle i've found. I'm no good at php nor smarty but I guess there is a way to adjust the corrupt href-string in the Cataloger templates...?

Will it help to report this as a bug in the Forge?
http://dev.cmsmadesimple.org/bug/list/47

After being in contact with the project admin I added my experience as a comment to the existing bug report:
http://dev.cmsmadesimple.org/bug/view/4781

Tried to reproduce this bug several times, without success. It works on all my servers. It seems to be a server specific configuration or other issue. There is not enough information to reproduce this.

Hmm...

What I do:
1. Add a User-Defined Attribute (Text-Area) in Extensions/Cataloger
2. Create a page in Content/Pages, choosing Content Type: Item Page
3. In the Text-Area described in point 1 above I use the MicroTiny button ("CMSMS Linker") to add a selflink to another Item Page in another parent.
4. Everything looks and feels great.....
5. Clicking that link on the Item Page in the front-end though gives this error:

Not Found

The requested URL /{cms_selflink href='anders-paulsson'} was not found on this server.

When ticking "View HTML" in the backend Text-Area the link looks like: Looks as it's supposed to, but that smarty tag is not being processed when published through Cataloger! When making the exact same cms_selflink in a CGBlog post or News item the resulting link works fine and looks like this in the frontend: Is it a problem with the MicroTiny editor?
Is it about Pretty URLs (internal url_rewriting) being activated...?
Is it as Jo thinks, a server specific configuration?

Boov hasn't been online since february... but I would love to hear if he found a solution to this...
Anyone else experiencing this problem right now? Or can figure out why it happens!?

Oh how I would like this to be resolved....!

Is it like boov said?

boov wrote:It seems as if the cataloger module does not know what to do with selflinks.

Or is it a server specific problem like Jo thinks?

Jo Morg wrote:Tried to reproduce this bug several times, without success. It works on all my servers. It seems to be a server specific configuration or other issue. There is not enough information to reproduce this.

In what part of my server could this issue occure? Would like to ask my host about it!

I have tried both the CMSMS standard MicroTiny editor and the TineMCE editor... Could one of the plugins for TinyMCE make any difference? I attached a screenshot of the standard configuration. The documentation:
http://www.tinymce.com/wiki.php/Plugins

Since boov is not attending this forum I have also sent an email to andiministrator who reported the bug in the Forge:
http://dev.cmsmadesimple.org/bug/view/4781

OK! I've been able to reproduce this. I had a problem with a trashed HD, so only recently it was possible to do some testing on this issue. However, at 1st, it's difficult to pinpoint what is causing this: Cataloger is passing the template to a standard CMSMS core template parsing method. Debugging this may take some time. I'm working on it.

Fixed in version 0.11.3 already released.
Have a Happy New Year.

Jo Morg wrote:Fixed in version 0.11.3 already released.
Have a Happy New Year.

Great news!! It works fine, thank you VERY much Jo! This forum and the forge really is a great opportunity to communicate directly with friendly developers like you. Happy new year!

Would appreciate a fix to my other problem as well:
http://forum.cmsmadesimple.org/viewtopi ... =7&t=64081
But this one was the most important

joxyzhan wrote:Would appreciate a fix to my other problem as well:
http://forum.cmsmadesimple.org/viewtopi ... =7&t=64081
But this one was the most important

The other problem is not a trivial fix. However Cataloger is going through major changes that should fix that and other bugs, and implement some of the features that have been requested. It means quite a bit of redesign and of re-implementing of the inner workings of Cataloger, so it also means the release of a major version. More news on this soon.

I have exactly the same problem with cms_selflink, but then with the module generator: http://dev.cmsmadesimple.org/projects/modulegenerator

What where the modifications you did to fix this ?

i have cataloger version 0.11.3 and I have the same problem.

Adding this to my template of module generator fixed it voor me: {eval var=$entry->content}.