Is anyone else seeing this on radiant 0.6.7?
If you delete a page and then view the page it still renders.
Not until you go edit and save another page, does the deleted page get cleared.
Steps to reproduce
1. Create page test
2. view page test on site
3. delete page test
4. view page test
Hi Folks,
I'm thinking of using Radiant to power my blog. I'm mailing to
find out if anybody else has had success using Radiant for this purpose?
and also in particular what extensions you would recommend installing?
Scanning GitHub and the documentation wiki so far I have:
* Paginated Archive
In terms of pulling down repos and updating a cloned repo, git is more
trouble than its worth. Tolerable nonetheless.
Sean Cribbs wrote:
Ben,
If you did a plain clone originally, run `git pull origin master`.
Sean
--
Posted via http://www.ruby-forum.com/.
Jason,
Yes, please file this on Trac as a bug.
Sean
jsmorris wrote:
Is anyone else seeing this on radiant 0.6.7?
If you delete a page and then view the page it still renders.
Not until you go edit and save another page, does the deleted page get cleared.
Steps to reproduce
1. Create page
Hello Martin,
I've written a little about my experience with using Radiant for a blog-like
content here:
http://depth-first.com/articles/2007/11/07/paginated-archives-in-radiant-cms-the-power-of-minimal-but-extendable-systems
But recently, I've started using Simple Log, which I now think would
I'd like to begin my work on extending the Radiant documentation, but
before that I'd like to get an idea of what others on this mailing list
are specifically planning to do so we don't duplicate effort.
Overall Goals:
* Make Radiant easier to setup for beginners via better wiki
documentation
*
Mohit Sindhwani wrote:
OK, I admit it. It's me. I'm the evil one! I really need to find the
time to get back to the mini-project for Radiant documentation. I have
been completely missing in action, working on an unrelated work
project. But, I hope to get back to the Radiant documentation
David Piehler wrote:
I'd like to begin my work on extending the Radiant documentation, but
before that I'd like to get an idea of what others on this mailing list
are specifically planning to do so we don't duplicate effort.
Overall Goals:
* Make Radiant easier to setup for beginners via
Sean Cribbs wrote:
If you did a plain clone originally, run `git pull origin master`.
Tried this and I got a list of all the files followed by : needs
update. Then the final output line was fatal: Entry 'README' not
uptodate. Cannot merge..
Checking my Extensions page in the admin UI, it
I'm experimenting with an idea for help documentation as an extension.
It obviously shouldn't cover getting up and runnining since you'd only
see it once you are running.
I was going to wait until this was more complete until throwing it out
there to the entire community, but since there's
I have to admit that rspec is still a bit intimidating, so I'm not
sure this is exactly the sort of spec you were looking for. Feel free
to point out everything that's wrong here and I'll try again.
===
--- standard_tags_spec.rb
+++ standard_tags_spec.rb
@@ -383,6 +383,13 @@
it 'r:random
Sean Cribbs wrote:
David,
Sounds like a great plan. One thing that had been mentioned in the
BoF session at RailsConf was screencasts. Anyone willing to make one
-- of decent quality and utility of course -- can submit it to me or
John and we'll post it on the main Radiant site.
Sean
Mohit,
I liked CamStudio on Windows, but I don't know if it's easily available
anymore.
Sean
Mohit Sindhwani wrote:
Sean Cribbs wrote:
David,
Sounds like a great plan. One thing that had been mentioned in the
BoF session at RailsConf was screencasts. Anyone willing to make one
-- of
13 matches
Mail list logo
