wobblemedia

Hi Harrison

It’s not the flexible content field. I guess I was trying to explain how I was hoping to use the fields.

When I create a new custom field group, that has a tab at the start and assign it to ‘default template’, then create a new custom field group with a tab at the top and assign it to ‘default template’, the tabs dont work, they stack vertically.

A good idea would be to be able to select field groups and make a new fieldgroup from the sub ones – if you get me?

Flexable content does what I’m looking for – cannot believe I’ve missed this.

Thanks!

Just a quick note, I have the page built and working fine. I just feel that leaving a box blank, or giving the users an extra box which will be left blank just adds confusion and makes documentation seem a bit unprofessional.

Thanks!

One other thing quintain which I just noticed. You said you are visiting the site periodically to see if the expiration is working. You can simply set it to expire minutes after you’ve made the post to test it.

Just sayin’

Also Quintain, I find it is best to minimize on use of plugins for wordpress sites. I know for a fact I had a few conflictions with this plugin and I would highly advise trying to hand code whatever you can.

before you go banging your head against a brick wall(like i do), I would suggest that you disable every plugin you are using and just test out contentsheduler on its own. If it works, start enabling plugins one by one, and see if it stops working.

Eyephone21 – I’m glad it helped. Hope it works well for you!

Quintain – The # lets you know that that code will not be executed. It’s just there for ‘commenting’ so you can write notes letting you know what is what when your .htaccess file is full of different commands.

In PHP this is done with // or /* */ for multiple line comments.
In HTML This is done with <!– this is a comment –>
If you view this pages source you will see <!– and –> all over it. It lets people know what they are looking at and how to better understand it.

So in your .htaccess file, the # is there to let you know what has placed that code in there, or what it does. For this particular site that i used cron with, my .htaccess file has comments letting me know that wordpress is using this code by saying #BEGING WordPress.

When you put in # your .htaccess file, the server will ignore anything that comes after it on that line.

in short, you can leave the # comments out, but its good practice to leave them in.