AdvancedContent

[NikNak]

Hi there

This last version in the previous post has been the first to work for me without a hitch, so I'm very excited about the possibilities.

Just as a thought - having an upload facility like there is on the news module, would be very useful. Perhaps it's worth consideration  further down the line. (or maybe not) 

Thanks again.

Nik

[NaN]

Thanks for your feedback.

Upload fields will be added to the block types image and file using the param upload=true.
I also planned to add the same features to the filepicker like there are in the TinyMCE filepicker. (using certain functions of the FileManager)
But it is not ready yet.
Before adding new functions i want to be sure that it is as stable as possible to release it in forge.

(Just noticed an "error" recently if using block type file/image: undefined index "maxlength"  Damn copy & paste  )

[NaN]

New release candidate is out.
You can download it from here: AdvancedContent v.0.3.2

Changes:

- fixed bug of blocktype dropdown/select_multiple where first item had an empty label if only the param "values" is used
- added some default template vars of the frontend to be also accessible in backend (e.g.: $page_alias - Notice: default template vars do not work if page is about to be added since the page and its vars does not exist at this time)
- added param "allow_none" to all content block types to specify if the predefined default value will be used if no value is entered

Official release date will be tuesday next week.

[NaN]

New release candidate is out again.
Did some errors that are fixed now.
You can download it from here (or check out the latest SVN revision):  AdvancedContent v.0.3.2


Changes:

- fixed bug where empty values where never be stored
- fixed bug where default value in frontend was ignored if the "allow_none" param was changed after an empty value has been stored
- added param "sortable_items" to create a sortable multiple select list
(select list will result in a table with checkboxes; only order of selected items will be stored and showed at the top of the list; unselected items will be appended in that order they are placed in the template)

[NaN]

Since someone asks for a specific block type that lists global content blocks i created a simple UDT to get a list of gcb names devided by a specified delimiter: http://wiki.cmsmadesimple.org/index.php ... t_gcb_list

So now you can create a dropdown or a multiple select list (even a sortable one) that shows your gcbs like this:

Code: Select all

{content block="gcbs" type="select_multiple" values=":::get_gcb_list:::" smarty=true sortable_items=true assign="gcbs"}
{assign var="gcbs_array" value="|"|explode:$gcbs}
{foreach from=$gcbs_array item="gcb"}
{if $gcb != ''}
{global_content name=$gcb}
{/if}
{/foreach}

[NikNak]

Hi there

Just uploaded your latest 0.3.2 (2010-05-31) from the forge hoping it would resolve the 'Cachable' and 'Searchable' buttons being remembered in the options tab. After submitting, the state would always revert to unselected.

The 'cachable' now seems to work, but the searchable is still showing the same problem.

Cheers

Nik

[NaN]

Damn!
Ever had that strange feeling that something is missed even if you're sure everything is fine?
I thought i've finished my to do list.
But i knew that i forgot something.
Hum... and that's it: I forgot to test the cache and searchable stuff
I will have a look on this.
Is it at least stored when you select it?
Or is it just not displayed right?

Notice: If you limit the access to a feu group the cacheable and the searchable option will be disabled automatically.
Since this (at least the disabled cache) is required by the feu module to check feu login.

[NikNak]

The checkbox doesn't store the selection.

Sorry to ruin your day -

Cheers
Nik 

[NaN]

It should be fixed now.
Just download the version 0.3.2 again.
(Didn't want to create a new version just because of this tiny issue)



Edit:
Sorry something is wrong with the forge.
I cannot upload the release.
But you can download it from the link i provided in the previous posts.

[NikNak]

Thanks   - but I couldnt get your previous link to download at all from dropbox.

[NaN]

Okay, it seems to be that the whole internet is corrupted and is about to scheme an intrigue against me ...  :o

...

No ... wait ... i believe the issue might have been with the latest zip file

...

Yeah, that's it.
It's a zip conspiracy!



Okay, so now the fixed release can be downloaded from forge again.

[NikNak]

Hi again

Just a bit more feedback - I'm getting a few problems with auto alias naming - The auto alias is not always being parsed to lower case and dashes. You then get the error: 'Alias must be all letters and numbers' -  when this happens the new content is not submitted and is cleared (could be v frustrating).

Also, when changing between content and advanced content, all unsubmitted text is lost from the main 'content' field.

Kind regards

Nik

[NaN]

Thanks for your feedback.

The auto alias is not always being parsed to lower case and dashes.

"Not always means" it only happens if you add a content (or clear the alias) and then switch the content type, right?
(I was only testing with existing pages ...  )
I added some lines of code to avoid the bug #4952 of the CMSms core and ... yeah, produced a new one.
This will be fixed in v.0.3.3.
(Is already fixed in SVN and my Dropbox)

Also, when changing between content and advanced content, all unsubmitted text is lost from the main 'content' field.

Is also fixed in SVN and my Dropbox.

[NaN]

By the way i wonder how many users actually use all three extra fields?
I'm planing to integrate support for the multi domain module.
Since you will need the assigned domain of the page when creating the menu it would be nice to be able to access this property in the menutemplate to create the link.

That means i would replace e.g. the extra3 field by a dropdown that lists the urls of the multi domain module.
So extra3 always would contain the assigned domain.

But this would cause problems to those users that already use the extra3 field for other things.
So how do you guys think about that?

[NikNak]

Hi NaN

Well I use all three extra fields in all my sites. I basically use it with a three column page layout, and assign each column an 'extra' field in addition to the content blocks. That way I can add individual smarty code to each column without the client being able to mess it up in the wysiwyg editor.

I guess there could be ways around it like looking up a GCB for each column based on the page alias - but it's quite neat for me currently.

However - a multi domain capability would have saved me endless pain with htaccess rewriting and symlinks on another project.
I dont know how the multi domain thing works, but I assume if a parent page is set up as a separate domain, then all child pages would inherit that - right? Is there a thread for this?

Cheers

Nik