Is Custom Properties compatible with Seblod

Hi,

I am giving Custom Properties a go for the first time. My site is Joomla 2.5.19 and I am using Seblod 3.3.2 (latest versions of both). From looking at some old posts on this forum I thought CP and Seblod may work together, but alas they are not.

When I install CP onto a site without Seblod CP loads straight away. Am I missing a configuration option or do these two components not like each other.

Thanks,

Lyn

Just to add to this, the issue is that the CP editor button will not display in my article edit area.

Ok I have solved my first issue and I have the editor button up.

From this post: solidsystem.it/forum/8-cp-20-for-j1617-p...lexicontent.html#719

I changed the code to:
$option = JRequest::getCmd('option','');
if($option == 'cck') $option = 'com_content';
$ces = CpContentElements::getInstance();

Now I just need my tags to display on the content page (they display in the module and on the search page) assuming this is a Seblod templating issue...

Lyn

Last time we tested Custom Proerties with Seblod the results were underwhelming.
Fact is that Seblod architecture is quite peculiar and not easily adaptable to CP.

We'll make new tests with the latest version of Seblod to see it the situation have improved and we'll let you know our findings.

We just tested Custom Properties 3.1.3 with Seblod 3.3.2.

Here's our findings.

a) Custom Properties is able to assign tags to Joomla-Seblod articles; in fact, from a database point of view, those articles are Joomla articles, albeit quite heavily tweaked
b) CP Tags content plugin - the one responsible for displaying tags at the bottom of the article - gets positively triggered
c) Custom Properties search module is able to retrieve tagged Joomla-Seblod articles
d) the <div> with the CP tags inside, that is appended to the article text, *is not* rendered by Seblod; somehow it gets discarded upon rendering

I understand that Seblod replaces the actual content with its own placeholders (e.g. ::introtext:: ... ::/introtext), so the article is stored with placeholders in lieu of the actual content. When the article is about to be displayed those placeholders are replaced by the actual content.

That leads to two effects:
1) when CPTags plugin processes the article it appends tags <div> at the end of the article's text, beyond any placeholders; I assume that being outside the placeholder is the reason why CPTags are not being rendered
2) when you search by text, using CP Search module, you search placeholders too. Eg: if you type 'introtext' you retrieve all articles containing the string 'introtext' and, in turn, because that happens to be a placeholder, you retrieve all articles.

Conclusion:
- compatibility between Custom Properties and Seblod is still very problematic;
- custom, ad-hoc, development must be done to CPTags plugin to place the tags <div> into a meaningful Seblod placeholder
- the search-by-text function should be heavily (and I stress heavily) modified to ignore Seblod's placeholders; or disabled altogether

Thank you for being so thorough at looking into this. I'm happy to disable the search by text function.

Re: custom, ad-hoc, development must be done to CPTags plugin to place the tags <div> into a meaningful Seblod placeholder

Is this something that I could engage your team to do?

Thanks again,

Lyn