I updated the code from the original TinyMCE extension to work with
other extensions. Unfortunately I didn't have time to test it very
well, so you might run in to problems. If you find bugs, please
contact me.
http://code.google.com/p/radiant-tinymce-extension/
Edwin
Op 11-okt-2007, om 23
Just add an empty page part to the pages you don't want to show in
your sub navigation and check for existence of the part in your
iteration. That is the easiest way :-)
Edwin
Op 6-sep-2007, om 18:55 heeft Travis Bell het volgende geschreven:
> Hmmm... I was hoping for a way to still have a
> there will be "properties" tab on page edit and user should be
>>>>> able to add properties specifying property name and property
>>>>> value. to improve performance of SQL queries properties can
>>>>> also have type attribute e.g. int, string, date and pro
I created a configuration extension to alter the Radiant
configuration through the backend interface. Most of the time, I use
the command line to edit the configuration, but this time another
administrator with no command line access needed to change
configuration options for an extension.
I'm having the same problem. Running from the Jargon branch, latest
revision. Besides that, I have the latest gem installed, but in the
gem the error doesn't occur.
I think running in development mode should not interfere with the
generators. I tried running in both development mode and prod
Hi,
I always overcome this problem by adding an empty page part to the
stylesheet. By using the tag you
can determine which pages should be added to the main menu.
Edwin
Op 2-aug-2007, om 11:32 heeft Mohit Sindhwani het volgende geschreven:
> Hi Everyone,
>
> After being away for a while,
in the past.
I can't say if this might cause the exploit, but the code could cause
race conditions which might give users access to the wrong information.
Edwin Vlieg
Op 23-jul-2007, om 2:02 heeft John W. Long het volgende geschreven:
> This is just an FYI, but in the interests
n the frontend.
I looked through all the Radiant code, disabled some parts (like the
LoginSystem), but can't find any cause of the weird session
behaviour. What am I doing wrong?
The full code of my extension can be found at Google Code: http://
code.google.com/
