CMS Made Simple Forums

To release a module all you do is upload an XML file (for ModuleManager) or a tar.gz file in the admin area of the forge.

Hmmm... heck tell ya what... I can start it if you'd like to work together on this... I think I have an idea for how to handle this as a module and  I could get the base together... but IMHO I think that dropping the in-template implementation altogether may not be a good thing, but I have some solutions for that... I have most of my mods at a stable stand point that I could get this rolling... Email me if you wish and let’s get rolling if you wish

ajprog wrote: To release a module all you do is upload an XML file (for ModuleManager) or a tar.gz file in the admin area of the forge.

Thanks, but I know how to release a module 
I just need to think about the programming stuff etc

Hi guys I'm trying to get this to work with the content_image tag. Here's what I have at the minute.
I've tried doing it using the capture tag as well.
Unfortunately neither of these (or the other million variations I've tried) work!

Basically I'm trying to import the title of the page (which will be a name) into the directory parameter for the content_image tag. I am creating a website which has a number of different pages for displaying info about members of the organisation and each member has a folder with the same name as the {title} in which their pictures are stored.

I suppose that I could create a different template for each different member but this would take ages and would be a pain so I am going to try this first.

If all else fails I may try creating another field which holds the content_image code and try and hide this from the user ( so they don't delete it by accident when they try to edit their information.

If anyone can help me sort my problem it would be awesome.

it'd be (if I put smarty on this.. Im not sure)

{content type=image block='image1' dir='images/:::title:::' class='image' label='Image 1'}

Hi JeremyBass

just upgraded and my content2 has gone... I can downgrade but is there a fix?

Thanx

R

hmm.. I never use {content2 ...}

I use something like

{content type=image block='image1' dir='images/:::title:::' class='image' label='Image 1'}

I'd start there.. but I can say this for sure.. 100%... it does work with 1.6.7.. hope this helps.. -Jeremy

I upgraded too but had no problems.
As i know nothing has changed to the contenttypes in the last CMSms update (1.6.7) so there should be no problem with upgrading.
What do you mean with "has gone"?
Are there any errormessages?
Did you try to set config['debug']=true in config php?

NaN, JeremyBass

I've fixed it pebkac on my part I had mismatched plugin and include files... any chance we could pop this i forge?

Cheers Rob

I would also like to see this in forge. Although it really SHOULD be part of Core

Wishful thinking 

Just created the first release in forge: http://dev.cmsmadesimple.org/projects/content2

This release also contains all mods of JeremyBass so far and some new features like redirect page if page is only visible to frontend users and user is not logged in or does not belong to the specified group. Content can also just be hidden without any action. You can even protect only certain content blocks or the whole page content. The page properties feu access and redirect page can be inherited by parent pages (if of content type "Content (Extended)).
Inheritance, feu access and redirecting only works in conjunction with the plugin {content2}.

Fixed a small bug with the option "Disable WYSIWYG editor on this page (regardless of template or user settings)" (i hope at least).

Please report any kind of feedback.

Cheers.

JeremyBASS wrote:
{content type=image block='image1' dir='images/:::title:::' class='image' label='Image 1'}

Just a note...
Notice that this won't work properly if the page is created since there is no title at this time.
So the used directory will be just "images/".

Hi NaN

I've just tried this and get:
Fatal error: Call to undefined method Content2::GetBackendSection() in /home/odchostc/public_html/sgtestv4/lib/classes/contenttypes/Content2.inc.php on line 44

Is it now important to use {content2 ...}  rather than {content ...}  ?

All was fine before using the files downloaded from earlier in this post.
Using cmsms 1.7

Thanks

Nik

*lol*

Sorry, wrong copy.
I uploaded a buggy version and deleted the working one
It really was tooo late yesterday.
This will be fixed soon.
(Is already fixed in SVN)

Just remove in Content2.inc.php around line 67 $this->GetBackendSection(); - this was just an experiment that does not work yet.

No you don't need the {content2} Plugin to use the content type at all.
Only if you want to use the frontend access function you need to use the modified plugin.

I just tried installing this from the files listed above, but I am getting an error about line 402 having an extra ) in it.

This is the line 402 from the file------>   if( !empty($blockInfo['label']) )

once I remove the extra ) i am now getting the following error:
Parse error: syntax error, unexpected T_VARIABLE in /var/www/dev/templates/lib/classes/contenttypes/Content2.inc.php on line 340

Any ideas?

Thanks for any help.