@Arik
There are actually three user-levels, not two -- Administrator,
Developer, and Basic/Writer. Personally, I'd like to see the Users page
show all three with the Basic user checked and disabled (permanently
checked) so that that option would be clearer.
The extension Andrew mentioned can
Arik Jones wrote:
What about publically-accessed user models in extensions? Do we have to
set up a member model or a completely new user model altogether?
In the thread I provided, Casper makes some comments about your question.
From a UI perspective, you probably don't want to mix the two c
Looks like I just sent out an email as HTML. Let's try this again with
plain text...
I'm reworking my Styles and Javascripts Extension to play nice with
Rails 2.0, and incorporate some things that John suggested and I'm
hitting a weird brick wall...
I have a TextAsset Model (with correspo
default STI implementation and just used the 'type' field -- didn't
try that one.
-Chris
Sean Cribbs wrote:
Chris,
Instead of moving it to the child class, I would put the validation in
the TextAsset class, but put the scope on the validation to :type, i.e.
validates_u
So I am writing my first rSpec 'tests' formally and I'm running up
against some questions on making this work within Radiant. Can anyone
shed some light on how to spec for the following items:
* My extension should create a tab in the Admin UI. It should be
before or after certain oth
aces or tabs'
@record.should_not be_valid
@record.should have(1).errors_on(:name)
end
Sean
Chris Parrish wrote:
So I am writing my first rSpec 'tests' formally and I'm running up
against some questions on making this work within Radiant. Can
anyone shed some light on h
e validations test_helper.
Instead do something like this:
it 'should validate the format of name' do
@record.name = 'abc'
@record.should be_valid
@record.name = 'cannot contain spaces or tabs'
@record.should_not be_valid
@record.should have(1).errors_on(:name)
en
One other thing. Is there a rake task to just run the specs for your
extension?
I see 'rake spec:extensions' but that runs all the extension specs
(including the built-in ones included with Radiant). Is there something
like 'rake spec:extensions:my_extension_name'
During the development of
Arik Jones wrote:
Will Radius ever support if/else statements?
I'd love to hear John and Sean's latest thoughts on this. I've often
felt that this was one of the main weak areas of Radius (and why there
are now several tags to fill the void).
In the meantime, I have an extension that I d
Ok, I've got a weird one here. In an extension, I'm attempting to add a
method or two to SiteController. I do this in the extension activate
method like:
def activate
SiteController.send :include, SiteControllerMods
end
Then, in /lib/site_controller_mods.rb I define a module to add meth
clue. I am JUST starting to hack into it :)
On Sat, May 10, 2008 at 12:50 PM, Chris Parrish
<[EMAIL PROTECTED]> wrote:
Ok, I've got a weird one here. In an extension, I'm attempting to add a
method or two to SiteController. I do this in the extension activate method
like:
This is probably more of a ruby question than radiant but here goes...
I have two controllers in my extension that I'd love to inherit access
rules (only_allow_access_to) since they share the same rules.
Basically, I'd like to put:
only_allow_access_to :index, :new, :edit, :remove,
:when
a list of features/benefits and usage.
Where to Get It
===
I'm not running on git so you get to use good 'ol svn:
https://secure.svnrepository.com/s_swanki/open/radiant/extensions/styles_n_scripts/tags/v0.2
Thanks and enjoy!
Chris Parrish
Sw
using serve.
Not yet. I remember you mentioning something about that idea several
months back -- glad to see it launched. Sounds slick.
-Chris
On May 15, 2008, at 7:54 PM, Chris Parrish wrote:
Hello all. John had asked me to create this some time ago as a
proof-of-concept for an enhanc
I fixed the issue mentioned below. The updated version can be found at:
https://secure.svnrepository.com/s_swanki/open/radiant/extensions/styles_n_scripts/tags/v0.2.1
This fix solves the error but still does not properly register the
created_by_id and updated_by_id fields in Stylesheets and Ja
Thanks for the quick responses you two. I'll be able to look at things
this evening and hopefully be able to add a few new specs and the code
you so wonderfully provided.
I'll also take a look at the 0.6.7 error that John mentioned.
BTW, if any of you know (or think you know) what's up with
Sean, I got an attachment but it looks to only contain the mailing list
email footer. Is the mailing list server whacking attachments possibly?
Could you send it to me directly or perhaps paste it into the body if
you want to share it with all...
Thanks,
Chris
Sean Cribbs wrote:
Chris,
Se
runs on Radiant 0.6.6 and 0.6.7 so far.
-Chris
Chris Parrish wrote:
Sean, I got an attachment but it looks to only contain the mailing
list email footer. Is the mailing list server whacking attachments
possibly?
Could you send it to me directly or perhaps paste it into the body if
you wa
uld get it run on a clean install (0.6.7) tho, with sqlite3 and no
other extension installed
it gives Could not find table 'config' error
On 5/18/08, Chris Parrish <[EMAIL PROTECTED]>
___
Radiant mailing list
Post: Radiant@r
no such table on db file
On 5/19/08, Chris Parrish <[EMAIL PROTECTED]>
wrote:
The Styles 'n Scripts extension makes use of Radiant's built-in
Radiant::Config settings (which get stored in the config table). So this
sound like a Radiant setup issue. (The only table my extension a
I just wanted to mention that I just noticed this change and am glad to
see it implemented in core as well. It eliminates the need for my
page_meta extension.
I too, like the inheritance idea (an optional attribute of the tag) but
I would also like to see a feature I had implemented in my ext
ritance of meta info be optional and
not the default.
Sean
Chris Parrish wrote:
I just wanted to mention that I just noticed this change and am glad
to see it implemented in core as well. It eliminates the need for my
page_meta extension.
I too, like the inheritance idea (an optional attrib
wrote:
Personally, I'd like to see inheritance of meta info be optional and
not the default.
Sean
Chris Parrish wrote:
I just wanted to mention that I just noticed this change and am glad
to see it implemented in core as well. It eliminates the need for
my page_meta extension.
I too, like the
appropriate
place in
your layout?
I haven't used r:meta yet, so perhaps I'm unaware of some particular
benefit
-Jim
On May 19, 2008, at 11:47 AM, Sean Cribbs wrote:
Personally, I'd like to see inheritance of meta info be optional
and not
the default.
Sean
Chris Parrish
I played around with the idea of creating an and
tag or even enhancing the tag to let you add
stylesheet/javascript content in addition to page part content.
The problem is that in either case you have to specify which file you
want (either explicitly or by first setting up a context to tha
What's the secret to creating a migration for my extension that changes
the data yet doesn't trigger the UserActionObserver?
I already figured out that I need to set MyClass.record_timestamps =
false so that I don't artificially change the updated_at field, but
changing a value and saving that re
ean Cribbs wrote:
If it's something that can be updated wholesale (i.e. the same for
every record, or derived on the same attributes), you can use
MyClass.update_all, which will not cause them to be loaded with
ActiveRecord.
Sean
Chris Parrish wrote:
What's the secret to creatin
Based on some feedback that I've gotten from the list (thanks all!),
I've added some new functionality and improved the existing.
NEW FEATURES
1. Added and tags for use in pages.
Based on the attributes, these tags will render:
* The url to a css or js file
* The c
nurilized wrote:
is there any way to call js/css files from anywhere of the page/layout?
suppose, i use one template and many subpages?
but i use different/extra css/js files on subpages (and also common), for
example i will use accordion script on a subpage and putting this on
template or on he
Anton Aylward wrote:
There __ARE__ pure CSS pull-downs.
Anton, I couldn't get to the link you provided so just in case I wanted
to make sure you and others were aware that you do need a bit of
javascript with suckerfish menus if you plan to support IE 6 or lower
(they only support the pse
I mostly only
use one stylesheet per website so it seems a bit overkill. Not to be
stingy with my tabs, but I think I'd like it better if the css and js
pages were both under one tab. I'm looking forward to seeing what
becomes of this extension.
Thanks,
Steven
On May 27, 2
ing that would be nice about putting them together
is that you could then make use of a "file type" combo box. That would fill
out the page a bit and give a person a little more to do. Also those lovely
icons would have a chance to help you sort out your file types.
-Steven
On May 27,
nurilized wrote:
Not sure I follow you. What do you mean by "no matter where they are
called from?"
i called from the content form
and it dumped everything in the place where i called it (inside body tag)
but i say it would be better if it is placed between head tags (but there
could be
I just noticed that nesting pages will apply the external filter on top
of the internal one. For instance, I set up a page like so:
Part: body, Filter: markdown
Part: another_part, Filter: none
//!<[CDATA[
my script content
//]]>
The output is:
//!<[CDATA[
my script content
I've just checked in a version (trunk -- not tagged) that adds
(same for stylesheet) which
renders a link to the external javascript or stylesheet. Stick a bunch
of those in your page parts and reference the part from your layout.
I'll roll the whole thing into a 0.3.1 release some time tomo
nurilized wrote:
why dont you git?
You guys are killing me. John's pushing me there today too ;-)
For the record, I use Windows and Eclipse (Aptana's RadRails) to do my
development. I'm used to, and like both very much. Right now, I can do
all my source code control right in my IDE wonder
Arik Jones wrote:
=
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /css/tinypixel.css.
=
I'm getting a 502 proxy error when accessing any asset from the styles n
scripts extension. Checking the product logs
Minor release with a few improvements and a new feature:
* Moved templates to Haml (niiicccee markup) so you'll need Radiant
0.6.7
* Added as="link" option to the and
tags to render an external link via or
Danny,
Are you using my new Styles 'n Scripts extension. If so, I'm quite sure
it isn't doing anything to accommodate a different root than plain old
'/' and will happily break things for you.
I would be happy to change this (for your need, to play nice with the
multi_site extension, etc).
Anton Aylward wrote:
My gripe is about the packaging.
I unpacked v0.3 into /vendor/extensions/styles_n_scripts/
and got:
Could not load extension from file: v0.3_extension.
#
As far as I could make out, v0.3 wanted to be installed in
/vendor/extensions/v0.3
Hmm, that sounds like somethi
Technically, its a Radiant issue but it shows up in Extensions that
still use ERB (or at least if your ERB templates have a or
tag). That's one of the reasons I went to Haml so quickly.
If you want to know more, read my ticket here:
http://dev.radiantcms.org/ticket/642
Anyway, by moving
Over the weekend I added file uploading capability so now you can upload
your stylesheets and javascripts right into the database -- Woo hoo!
This is my first stab at using Rails uploading and RJS so I'd really
love any feedback anyone has to offer.
You can get it here (while supplies last):
Danny,
I was hoping to include a fix for this issue with v0.4 but did not get
to it yet. But, for now, you can already solve this issue using the
config settings that I have built into the SnS extension (don't know why
I didn't think of this sooner).
To do this you edit the custom_settings.
Thanks for the heads up, Jay! I've fixed the issue and just released
SnS v0.4.1
As it turns out, I actually needed to make the date conform to HTTP
header standards via:
response.headers['Last-Modified'] =
@text_asset.effectively_updated_at.httpdate
which, as you pointed out, is a string
Jay Levitt wrote:
Yep, that works too!
Good. Let me know if anything changes.
BTW, for others reading the list, you will need to clean out the old
cache to get the new date format to take (as Arik mentioned). This is
done automatically whenever you save any asset (javascript or stylesheet
@Jason - I have been doing things this way for a while in my other
extensions and never had any problems. I remember checking it with SnS
when I first built it with 0.6.6. too. That said, I like your approach
better and will go with that in the future. Thanks for the head up -- I
doubt I wou
I see that Casper already sent a reply but I thought I'd mention the
Styles 'n Scripts extension here since it was made to make things like
this simpler. You would simply use the or
tag in your Page/Layout/Snippet to render the thing you want:
generates:
while...
generates:
/css/my
John and Catherine Allen wrote:
Chris,
Thanks - in fact I had successfully installed the Styles 'n Scripts
extension but was not clear about how to make use of it. I'll try the
tag approach.
John
Both the and tags have explanations if you
click on the "available tags" link on the "Edi
After posting to you on the other thread, I came over here and see that
Casper has pointed out:
Casper Fabricius wrote:
Yes, well that's because you are running radiant in sub-directory; at
http://allenlux.dyndns.org/radiant3/ rather than
http://allenlux.dyndns.org/.
I also see Sean's respo
This issue was brought up some time ago so it might be worth checking
the maillist history, but I'm not sure anything was ever implemented.
One of the interesting things brought up , if I remember correctly, was
the mention of Rick Olson's acts_as_draftable plugin. It might be worth
looking i
First of all let me say, Jim, that I *really* like your analysis of the
"Review Drafts" use case. You are so right that, as a reviewer, I want
to focus my attention on the changes not the stuff that's the same. I
really hadn't given this issue much thought before you brought it up.
That said
10 space characters and it started with v0.6.7? I can almost guarantee
it's this: http://dev.radiantcms.org/ticket/642
I'm guessing that you have an extension with it's own Pages
edit.html.erb file (or at least contains the textarea element for the
page edit form). If so, you can:
* Wai
That's awesome, Jim. I know it's something John has talked about adding
into Radiant core. He's got some good UI ideas about how to make that
most useful -- you might talk to him about it.
A Radiant Help system is also the reason why I like Mohit's breakdown --
but with a slight tweak. If d
David Piehler wrote:
Chris Parrish wrote:
1. Using Radiant - This section covers all the stuff users do from
within the Radiant Admin Interface
2. Installing Radiant - This section covers getting the source
(including extensions) and getting it to run
3. Extending
Jim Gay wrote:
I want to add regions into the interface for radiant-help.
Is this possible? If so, can I get some pointers on how to go about that?
-Jim
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/
Will Emerson wrote:
Through trial and error, I got the rails_support extension working in
0.6.7 and Rails 2.0.2. But now I'm trying out the share_layouts
extension and I'm having some problems getting it to work. In this
project, my app is already made into an extension and I'm trying to
integrat
ed -- sorry.
-Chris
Chris Parrish wrote:
Will Emerson wrote:
Through trial and error, I got the rails_support extension working in
0.6.7 and Rails 2.0.2. But now I'm trying out the share_layouts
extension and I'm having some problems getting it to work. In this
project, my app is alre
irectory|css
but you are right production.log says it cannot find text_assets table and
right there is no such table on db file
On 5/19/08, Chris Parrish <[EMAIL PROTECTED]>
wrote:
The Styles 'n Scripts extension makes use of Radiant's built-in
Radiant::Config settings (which
talled. In fact, it should be as easy as something
like this:
task :minimal_environment do
Radiant::Initializer.run do |config|
config.extensions = []
end
end
Then we could make db:bootstrap and anything else that needs to
prevent extensions from loading depend on that instead of t
I just outlined the fix in a reply to Sean's post. It's a little more
elaborate (though I think more elegant) than I'd post here.
If you're trying to get it to "just work for now" you can simply comment
out the following line from the styles_n_scripts_extension.rb file:
include CustomSetting
Sean Cribbs wrote:
Chris,
We might be able to make a rake task that loads the environment with
no extensions installed. In fact, it should be as easy as something
like this:
task :minimal_environment do
Radiant::Initializer.run do |config|
config.extensions = []
end
end
Then we
This may be more Rails than Radiant but can anyone give me a hand with
this one...
How do I execute ActionController::Routing::Routes.reload! for a running
instance of Radiant from a Rake task? It works fine if I trigger it
from within the app but I need it to run from Rake and it seems that
your extension, let me know. I'd sure love to avoid a 20 car
pileup there if a user has multiple extensions installed.
-Chris
Chris Parrish wrote:
This may be more Rails than Radiant but can anyone give me a hand with
this one...
How do I execute ActionController::Routing::Routes.re
ing (#2). If I use a before_filter to call my
#show_text_asset action and it finds and renders the script/stylesheet,
how to I then prevent things from proceeding on to #show_page?
Will rails let you set up a before_filter against only one action, anyway?
-Chris
Alex Wayne wrote:
Chris Parri
Hmm. Will give that a whirl then. I'll let you know. Thanks.
-Chris
Alex Wayne wrote:
Chris Parrish wrote:
My question was originally tied to approach #1. I could use a Rake task
to change the "javascript_directory" but couldn't get the
already-running server to rel
John, have you ever considered changing the name "developer" to
"designer"? I think it'd be more clear.
Also, I'd think clarity could be further improved by:
* Showing that there is a Basic user privilege level that is applied
when Administrator and Developer are not checked. It's no
Um, this thread's starting to deteriorate a bit.
@Alex - As you mentioned, I'm starting to like the component-ized
approach as it makes it possible for extension builders to integrate new
roles without breaking the UI (which oddly enough uses checkboxes =
component mentality).
@ Anton - My c
Sean Cribbs wrote:
I feel we should let the UI changes drive that kind of change.
I originally posted to record my thoughts and possibly help others
understand what Radiant was "thinking" with it's roles. I
wholeheartedly agree with you here Sean. I see much of this already coming.
-Chr
Jonathan McCoy wrote:
Chris Parrish wrote:
Interestingly, in one of your later posts, you define "Developer" and
"Designer" separately where "Developer" was working outside of the
Radiant UI (including RoR and DB tasks). And where Developer got into
(x)html or
I'm completely lost here. Can anyone shed some light on this?
In the SnS extension I have created the following...
In styles_n_scripts_extension.rb (activate method):
SiteController.send :include, SiteControllerExtensions
In the /lib/site_controller_extensions.rb file:
module SiteController
Can anyone provide some insight -- or even just
suggest some way to start tackling this?
-Chris
Chris Parrish wrote:
I'm completely lost here. Can anyone shed some light on this?
In the SnS extension I have created the following...
In styles_n_scripts_extension.rb (activate meth
Only tests (specs, actually).
Alex Wayne wrote:
Does the site work ok when you boot the server? Or is it only tests
that are broken?
-Alex
http://beautifulpixel.com
On Jun 25, 2008, at 7:28 AM, Chris Parrish wrote:
Anyone?
Further testing shows that when I don't include my module,
Use "rake spec:extensions EXT=your_extension_name" to just run the specs
for your extension.
By the way, does anyone else think it would be useful to run specific
spec(s) within an extension?
Perhaps using syntax like:
rake spec:extensions EXT=your_extension_name
FILE=app/controllers/my_c
Chris Parrish wrote:
Use "rake spec:extensions EXT=your_extension_name" to just run the
specs for your extension.
Oh, and you run it from the project's root - not the extension's.
-Chris
___
Radiant mailing list
Post: Ra
Alex Wayne wrote:
Thats quite odd. Are you sure you are running the latest rspec gem?
Try a
gem install rspec
-Alex
http://beautifulpixel.com
I've had troubles using the rSpec gem because Radiant ships with its own
version of rSpec and rSpec on Rails. Whenever I tried to use the gem,
rS
All this discussion of yet more "" tags and another recent
thread with the desire to pass values to snippets has me thinking of
digging up my old conditional/variables extension. I'm sure it needs
revamped for the current versions of Radiant and I'd like to clean up
the syntax some but, mostly
Thanks for your response and kind words, Jim. See my comments below...
Jim Gay wrote:
I agree that the list of if_this unless_that can get very long, but
there is a benefit in that the intentions of the code are clear.
I remember seeing emails about your extension and being very
interested in
Tim, hanks for the kind words and interest in the Styles 'n Scripts
Extensions. I am about to release a new version of SnS which
incorporates Shards. I've had several ideas to "improve" SnS but that
always seemed like extensions in their own right. Once this is done, I
will be offering some e
Alex Wayne wrote:
I whipped up a quick extension today that some might find useful. I
searched around a little and didn't come with any solutions that I was
happy with, form a functional or aesthetic standpoint.
Nice work.
It adds a "Settings" tab that provides a nice looking interface to
Thanks for the write-up. I've been using Shared Layouts but I learned
a few things I didn't know from this.
I do have two questions from what you've said, though
Sean Cribbs wrote:
Second, if you want your controllers to have more context within the
rest of the site's static content, you can
Some new features, refactoring, and bug squishing. Latest version can
be found at:
https://secure.svnrepository.com/s_swanki/open/radiant/extensions/styles_n_scripts/tags/latest
For those with inquiring minds, the changes (taken from HISTORY) are:
Lots of improvements here. Some new features
Well, a few of you asked for it and it turned out to be pretty simple so
here you go...
https://secure.svnrepository.com/s_swanki/open/radiant/extensions/sns_sass_filter/tags/latest
SASS filtering for Styles 'n Scripts!
I still consider it a v0.1 release -- mostly because I didn't spec this
on
I did say more coming soon, right... So here's another.
This time it's the SnS Minifier Extension found at:
https://secure.svnrepository.com/s_swanki/open/radiant/extensions/sns_minifier/tags/latest
Again, early release (v0.1) so please give me feedback.
From the README file:
= Styles 'n Scrip
New release! You can find v0.1.1 at:
https://secure.svnrepository.com/s_swanki/open/radiant/extensions/sns_minifier/tags/latest
Thanks to Tim who found this naming issue (see below). What can I say -
it was getting late.
-Chris
Tim Gossett wrote:
I got the following error for /admin/css/n
Tim Gossett wrote:
On Mon, Jul 7, 2008 at 1:30 AM, Chris Parrish <
[EMAIL PROTECTED]> wrote:
You will need the Styles 'n Scripts extension installed for this to work
and you
will also probably need to change your project's environment.rb file to
twiddle
the load order (t
Tim Gossett wrote:
None of the models would be renamed (right?), so users should be able to
swap out the existing extension directory for a renamed one and get off
without a hitch. If I had a few spare moments, I'd try it for myself right
now... maybe there'd be a clash with the version number in
Since the all / find / require_all / inclusive attribute is both
required and boolean (yeah I know XOR's been mentioned but I'm not going
there), why not try to include that condition in the rest of it somehow?
(notice that the name "part" is singular)
So in this example, you'd have 3 diff
Jim Gay wrote:
On Jul 8, 2008, at 8:16 PM, Chris Parrish wrote:
Since the all / find / require_all / inclusive attribute is both
required and boolean (yeah I know XOR's been mentioned but I'm not
going there), why not try to include that condition in the rest of it
somehow?
(n
In your example, Sean, you create a StatsController that inherits from
ApplicationController (which is the default if you use Radiant's
controller generators). Anyway I've been getting all kinds of errors
with my specs and banging my head against a wall only to *finally*
realize that Applicati
y been dragging my feet there.
-Chris
Tim Gossett wrote:
Not to pre-empt Chris Parrish, but I've renamed the styles_n_scripts
extension to sns as mentioned earlier on this list.
I'm a recent GitHub convert, still floating on a cloud of GitHub Zen,
so I've mirrored all of Chirs&#x
You have my vote for Radiant Cap recipes.
-Chris
Sean Cribbs wrote:
I recently deployed a Radiant project on a new RailsMachine VPS, and I
found the best way to avoid these issues is to create your local git
repository in the project, and use Capistrano's option to copy a
tarball to the serve
You can solve item #2 using and multiple stylesheet
files. Just like you can use the to reference multiple
libraries and create a one-script-to-rule-them-all master to just serve
up one library file, you can also incorporate many stylesheets into one
master.
So you could create:
main.css
Jim Gay wrote:
I haven't yet looked at it. I haven't used Sass much. I like some of
the features that it adds, but it removes some control and I'm not
ready to tackle it yet since I've run into trouble with Haml and the
Help extension (it has some lines that are completely ignored by
Haml... b
Ok, item #1. Unfortunately, this is hairier than you'd think:
1. Pages have an entirely different context than stylesheets and
their tags don't exactly snap in (what exactly is the parent of a
stylesheet? the slug?) Basically, I'd have to rebuild these tags
for stylesheet/javas
'url') do |tag|
copy/paste/massage the page's url tag into this tag
end
... same with ...
end
Bonus points if you figure out a slick way to keep things DRY by reusing
the code from the pages tag definitions.
-Chris
Chris Parrish wrote:
Ok, item #1. Unfortuna
Minor changes here...
https://secure.svnrepository.com/s_swanki/open/radiant/extensions/styles_n_scripts/tags/latest
https://secure.svnrepository.com/s_swanki/open/radiant/extensions/sns_sass_filter/tags/latest
Styles 'n Scripts now belongs in a directory named "sns" like:
[your radiant project]
Tim Gossett wrote:
Any changes to sns_minifier, Chris
No, it works fine with the new version of SnS (just the Sass Filter
needed an update).
-Chris
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/sea
Joe Van Dyk wrote:
Hi,
I'm new to Radiant, but not Rails.
So, I'm seeing that stuff like the layout and CSS is entered through
forms and saved to the database, and aren't contained in version
controlled files.
So, how does that work? I mean, how do you deploy changes? Just by
copy/pasting th
Ooh, WMD's gone MIT licensing. Now this is nice to see.
One more thing to play with...
-Chris
Oli Studholme wrote:
Hi All,
Has anyone added the WMD markdown editor to the admin interface yet?
Or any WYSIWIG editor? I’m looking for some advice on the recommended
way to do so.
peace - oli
Ok, that's twice in one week (Jim Gay just asked for the same thing). I
don't think this tag belongs in SnS since it depends on Page Attachments
too but a new extension for it might be nice.
Anyone willing to whip up a mini-extension that simply adds the
necessary image tags to the Stylesheet
1 - 100 of 187 matches
Mail list logo
