Hi Guise

I have only my phone for internet access at minute so answers are not complete, but I'm pretty sure SEBLOD stores fulltext in the introtext column. Check it out in db...

It goes something like this:

Hi, thanks for the reply: I know SEBLOD does that by default (storing also fulltext content into introtext DB field, breaking the standard joomla compatibility), but my question is about changing that default to preserve compatibility (fulltext content into fulltext DB field as raw data, without ::cck...).

I changed the storage type of the fulltext field but it is not working when adding/modifying an article: the fulltext content gets lost and in the fulltext DB field I found "::cck::1::/cck::".

The weird thing is that if I put the fulltext content directly into the DB field (via SQL), the visualization on frontend works! As if reading works, writing does not.

Any clue?

Thanks!

Giuse

Anyone able to help me?

cheers

Giuse

Hi giuse

So what happens when you create your own fulltext field rather than using art_fulltext?

Not tried it. Is it the same result (::cck:: etc)

Bucklash

Hi,

You can change storage with SEBLOD by using standard, JSON, or 'custom storage'.

Guise, SEBLOD to render your content need to make a relation between a Joomla article and SEBLOD data. To do this SEBLOD is saving at the minimum the cck id into introtext field (::cck::id::/cck::). It works such as a Joomla content for this. It's a solution to not change com_content table structure and stay full Joomla compatible (SEBLOD is using Joomla article view to render SEBLOD data).

We don't advise to save other SEBLOD data into introtext field by using custom storage and so just the cck id in the introtext.

sorry but my question is about fulltext, not introtext: I see that fulltext by default goes into introtext DB field while I need it to go to fulltext DB field as in standard Joomla. Changing storage for art_fulltext did not work.

I hope to have clarified, thanks a lot for your help!

Giuse

Hi Giuse

It seems like you want SEBLOD to work a certain way, and because it doesn't you are trying to make it fit. 

Why are you trying to do with fulltext ?

Let's see what the Seblod way is before changing any default behaviours

For me: Rather than using Joomla!'s page break thingy to get fulltext, with SEBLOD I can create a button that allows a user to see a fulltext wysiwyg etc 

I can use Seblod to list articles and display intro text that can link to articles that show full text...

Bucklash

Hi,

@Bucklash, thanks!

@Giuse, you can create a new "Fulltext" field by using standard storage linked to a new column in the table of your content type or using the fulltext column of com_content table by using custom storage with "fulltext" (for this last one use the existing fulltext seblod field and change storage option).

Thanks.

Hi, @Bucklash: my purpose is to keep compatibility of Seblod articles with Joomla articles storing introtext into introtext column (also if with the cck ID that I know being currently mandatory for linking Joomla to Seblod) and storing fulltext to fulltext column, since it seems as we have this configurability in Seblod.

Cheers

Giuse

Hi,

This is an interesting topic.

Bes, I've been always wondering why SEBLOD needs to store its tags (::cck::id::/cck::) exactly in the intro text field? This field is used by most of the other Joomla components and modules to get the important intro text of an article and storing these tags there brakes compatibility. Resent example is: I've bought an Autotweet Joomla component which was grabbing the SEBLOD tags for the massage of the tweet instead the content of my SEBLOD description filed. Could you not make SEBLOD store its tags in some other com_content field, or even better on SEBLOD install make a spacial tag field in the com_content table?

Best regards,

ricco

Hi,

@ricco, introtext is the better possibility since another proposal. This Joomla field must be used in intro view too. Introtext is currently the best choice.

@Giuse, please make a test on a fresh Joomla/SEBLOD install

Thanks

Hi Bes, I did the test on a fresh installation but it seems not to work. I repeated everything again with a free Joomla/Seblod: cloning Article type into an Article2 type where I created a new "real fulltext" field and removed the defaul fulltext. The new "real fulltext" field has the desired storage (Standard|Article|fulltext) but the fulltext does not go into the fulltext column, where instead I find "::cck::1::/cck::"

I also noticed that setting the "Auto Read more" to NO in the "CCK Storage Location - Joomla! Article" plugin makes Seblod to not write anything in the fulltext column, while if left to YES (default), as said above, I find "cck::1::/cck::"

Could you please investigate this?

Thanks

Giuse

@Bes: thanks for your reply but it is not working here and it is why I started this thread: I cloned the article content type into a "Joomla Article" where I changed the fulltext field into "Joomla fulltext" modifying the storage to Standard|Article|fulltext. Infact the last line in #__cck_core_fields is

======

(542, 'Article Joomla Fulltext', 'article_joomla_fulltext', 10, 'wysiwyg_editor', '', 1, '', 'Select an Option', 3, '', '', '', '', '{"editor":"","width":"100%","height":"280","import":""}', 0, 255, 32, 0, 0, 0, 0, '', 1, '', '', '', '', 0, 0, 0, 0, 0, 0, 1, '', '', 'standard', 'article_joomla', 'joomla_article', '#__content', 'fulltext', '', '', '', 0, '0000-00-00 00:00:00');

======

Now, when I create a new "Joomla article" from the backend, fulltext is stored inside introtext column with custom storage (together with introtext)... :(

This is what I am trying to do with fulltext but with no success.

Is there a bug in Seblod configuration that, regardless of storage type, it always uses the default values or should I do something different?

Thanks a lot!

Giuse

Hi Giuse,

Can I ask you why you specifically want to use an ARTICLE with storage Standard|Article|fulltext.

Why not just create a new content type with field WYSIWYG with storage :

Standard | Article | mytextfield

and then just keep on creating Joomla Articles where you want?

hi, because I'd like to have fulltext in fulltext column like in standard Joomla, so that for example plug-ins that read from the DB are compatible.

The content type might be any one (not Article necessarily) but I have not succeeded in writing anything to the fulltext column by cloning article type (via batch operation) and using storage type Standard|Article|fultextl, that's my problem in this thread.

Thanks a lot for your feedbacks so far

Giuse

Hi, any news on the problem of storage of a WYSIWYG field (cloned from fulltext) into fulltext column...? Has anyone succeeded in doing that?

cheers

Giuse

Please anyone can support here, Seb or someone else from Octopoos?

I recap here the exact steps:

• fresh joomla 3.5.4 and Seblod 3.7.2 install
• duplicated "Article" content type via select&Batch copy into a "Joomla article" content type
• edited "Joomla article" content type:
  • added a new text field "cleanfulltext" with storage "Standard|Article|fulltext"
  • removed standard article fulltext field
• Add a new Content:
  • "bla bla bla" typed into introtext
  • "gasp gasp gasp" typed into "cleanfulltext".

  Save.

Result: in the DB I find

• introtext column => "::cck::1::/cck::<br />::introtext::<p>bla bla bla</p>::/introtext::" => OK
• fulltext column => "::cck::1::/cck::" => WRONG, I should find "gasp gasp gasp"

Don't we have a bug?

thanks

Giuse

Hi Giuse,

The cck id need to be saved in fulltext field too (such as introtext) to let SEBLOD working when the introtext is not displayed.

Thanks

Hi Bes, thanks but also changing storage of fulltext into "Custom|Article|fulltext[fulltext]" does not work (the fulltext column holds just the cck id and not the fulltext content....).

Does it mean that it is not possible to change anything of the default behavior of Seblod? I mean:

• introtext storage must be only "Custom|Article|introtext[introtext]"  => this is written in the online manual so well known
• fulltext storage must be only "Custom|Article|introtext[fulltext]" and cannot be changed to any of
  • Standard|Article|fulltext           (since it is not compatible with holding cck id)
  • Custom|Article|fulltext[xxx]      (to store fulltext into fulltext column, it is the purpose of this thread, together with cck id)

both of these are not supported and fulltext must go to the same column where introtext goes. Am I correct with this (it is not specified in the online manual that's why I am asking)?

Thanks a lot

Giuse

Hi Giuse

I'm Probably not able to help, but what extensions are you using?

What exactly are you trying to do?

I know you want to use fulltext, but what is it you are trying to do with it, are you using Roksproket by Rockettheme, or Something by Joomlack, or Yootheme...?

Hi, I am trying to have introtext into introtext DB column and fulltext into fulltext DB column to have maximum compatibility with standard joomla so that I can:

1. pass from Seblod way to Joomla way just turning off seblod component on my test site, to test behavior and compatibility of components and plugins with and without seblod
2. share articles between a seblod based site and a not-Seblod based site.

In these cases, if introtext and fulltext are in the usual places (i.e. in the standard DB column) this is possible: when turning off Seblod or sharing with a non-Seblod site, I just need to enable a content filter on frontend (using ReReplacer) that strips away the cck Id and everything else is fine and compatible.

If introtext and fulltext are stored together into a single DB column (introtext) than it is not possible.

Frankly I am a bit surprised, since this is the 21st post and still I don't see a clear answer if this is possible or not: I have been suggested to

• change storage of fulltext => tried but seems not to work
• create a new field to store fulltext => tried but not worked
• create a new content type with a new field for a new version of fulltext => not worked
• allow cck id to be stored into fulltext with custom storage => done but nevertheless the fulltext field is not stored into fulltext DB

so I am wondering: is my request feasible or not? If it possible, I would kindly like to know how, if it comes up that it is NOT possible (strange that it was not said at the first post :) ), fine, I give up but for other people I think it should be added into the FAQ/Manuals that "fulltext storage cannot be changed in any way from its default".

I hope to have clarified.

Thanks a lot to whom can answer definitely :) :)

cheers

Giuse

Hi,

Try this and report back please.

Regards,

ricco

https://drive.google.com/file/d/0B94jDt8p2n8GYWJGeVp2OGFnbkU/view?usp=sharing

Hi, tried to change fulltext storage as suggested but didn't work. Also tried to change into "Custom|Free|fulltext" and also "Custom|Free|fulltext[fulltext]" to hold cck id, but no luck....

Don't change the fulltext storage, create a new one.

You could probably messed it up. There should be a way to write in the fulltext column!

cloned content type "article" into "joomla" article. Added a new text field with storage "Standard|Free|fulltext" as suggested and excluded standard fulltext field.

New content: after save, the new field holds just cck id :(

Also tried with storage "Custom|Free|fulltext[fulltext]" into #__content. Nothing is saved...

Could you try on a clean Joomla+SEBLOD install without cloning, please create the content type and the fields from scratch.

Hi Ricco and thanks a lot for your useful suggestion. I made a lot of additional tests and here it is what I have discovered:

• fulltext CAN be written to fulltext DB column only creating a new content type from scratch and setting the storage to "Standard|Free|fulltext" option = #__Content (as per Ricco suggestion).
  • With this configuration, the typed fulltext goes to the fulltext DB column and there is no cck Id in the same field so it's not clear for me why Seblod needs it for the article and does not need for another content type that is equal to the article one: does Seblod really need it? Not using it would enhance the "not Joomla hacking" statement of Seblod since the only change to standard Joomla would be the inclusion of cck id to introtext DB column with the custom format. Any feedback from Octopoos team on this?
• duplicating article content type and making the same modifications (cck_core_fields, cck_core_types) instead of creating from scratch seems NOT to work: fulltext not written to DB. Evidently Seblod does something different if it recognize that the content type is article.... what? I don't know. That means that to have fulltext into fulltext column you have to create a new content type repeating each single field from article into the new type.
  • With the duplicated article content type (the one that does not work, making fulltext not being written to DB), the "Auto Read More" setting of the Article Storage plugin has a curious effect: if set to YES (default) => the fulltext DB column is filled with cckID; if set to NO => nothing is written to fulltext DB column. This again let me wonder if Seblod needs really the cck id in the fulltext.

Feedback and comments?

cheers

Giuse

Thank you Giuse.

Hi guys, 

1 - first of all I'm completely agree with "ricco". The introtext and fulltext are the most used fields for a lot of plugins. This mean don't have Joomla plugins etc. compatibility with Seblod.

2 - Can anyone from Octopoos team answer to this last question / observation from "Giuse" ?

3 - @Seb, you wrote:

Well, from joomla 3.7 will be introduced the Joomla Custom Fields (the develop of the feature is yet finished).

So, Why not use this feature Creating, also manually, a "Hided" Custom Field where to wire Seblod ?!? In this way all the standard most used Joomla fields like introtext and fulltext will remain free of "hack", completely compatible with all Joomla Plugins etc. ...

I fully support this: Seblod would be greater with full Joomla compatibility and the missing piece is just non-Joomla usage of introtext/fulltext. The new custom field in Joomla 3.7 is perfect for this. Can we hope for this adoption?

cheers

Giuse

Hi guys,

I'd like to receive some answers/comments here, in special from Seblod Team before to add a "feature request" on GitHub.

Please, Are there any special rules to add "features requests" on GitHub ?

Thanks to all...

This would break backwards compatibility so it is not likely it is going to happen soon.

Hi everybody,

Thanks for your interesting discussion!

I don't understand this statement "The introtext and fulltext are the most used fields for a lot of plugins. This mean don't have Joomla plugins etc. compatibility with Seblod."

IMO it's the reverse or I miss something. By using introtext and fulltext SEBLOD is compatible with the majority of Joomla plugins and modules.

About Joomla 3.7 or any Joomla version, the matter is not about where to save the cck id but how are working the majority of Joomla plugins and modules. Imagine the cck id is saved into another field, no more Joomla plugin or module will work with SEBLOD because these plugins or modules are not using the new field. 

Thanks.

Hi Bes and Klas, 

many thanks for your answers.  @Seb: So, recapitulating, what we are writing here is that:

1 - SEBLOD is saving the cck id into introtext field (::cck::id::/cck::). About this you wrote:

2 - SEBLOD is storing also fulltext content into introtext DB column field (::cck::id::/cck::). About this you wrote:

Now, the introtext and fulltext are the most used fields for a lot of plugins, as "Ricco" yet explained for example (2 Level 1). A lot of plugins / components use the standard Introtext / Fulltext, but when they grab it they also grab the (::cck::id::/cck::) and Fulltext. So, always, for Seblod need to be developed another special plugin. Really an awful situation. Now, trying to solve these issues:

2 - Can anyone from Octopoos team answer to these last tests observations/questions from "Giuse" (2 Level 6) ? This could solve the second point.

1 - Trying to find a new solution, Ricco asked: 

And you replied:

Following this  and trying to find an option to make the Seblod relation/connection I made a suggestion / question:

Well, from joomla 3.7 will be introduced the Joomla Custom Fields (the develop of the feature is yet finished).

So, Why not use this feature Creating, also "manually", a "Hided" Custom Field where to wire Seblod, where "to save" the (::cck::id::/cck::) ?!? In this way all the standard most used Joomla fields like introtext and fulltext will remain free of "hack", completely compatible with all Joomla Plugins etc. ...

Hope is more clear now :)

PS Why not have a way to recover a post link here in the Forum, for example leaving a linkable date on the right of the posts. This would permit to insert a link to a post and save a lot of time and do shorter posts :D

Thanks Joomleb.

But I repeat, this statement "A lot of plugins / components use the standard Introtext / Fulltext, but when they grab it they also grab the (::cck::id::/cck::) and Fulltext. So, always, for Seblod need to be developed another special plugin. Really an awful situation." is false.

By doing like this into SEBLOD, the majority of Joomla plugins/modules are compatible with SEBLOD.

We need to be on the same page about the point above. If not this discussion has no sense.