On 23 Jan 2011, at 19:04, Carl Youngblood wrote:
Hello, we're running a Radiant installation and we're experiencing
very slow load times. Here's our site:
http://transfigurism.org
We're running it on a linode 512 vm. The site uses the
radiant_rss_reader extension to construct many
Thanks a lot for taking the time to respond, Will. I have commented out
those lines and restarted Apache, but I'm still experiencing the same exact
thing. I have confirmed that the ruby processes I see spiking in htop are
new ones, so I'm certain that my changes are being read.
Thanks,
Carl
On
Good catch. Looks like I can start with it as a basis for my
extension.
Thanks.
Pete
On Jan 23, 12:00 am, William Ross w...@spanner.org wrote:
On 23 Jan 2011, at 02:30, Cleverlemming wrote:
Hail Caesars,
I see how to use the r:if_url matches tag to server content
conditionally based on
I am new to Radiant, and not a (real) programmer, but I am persistent
and willing to try things. Here's what I'm trying to do with the tags
extension: extract the number from the output, style it with css as an
em element, remove the parentheses around the number, and move the
number to before the
Thanks for the advice Anton. Pages are coming up fast when they are accessed
with a referer header and when they have recently been generated by Radiant.
But they are taking 30s when I type the URL in directly and when I click
refresh in a browser. All this 30s is spent by Radiant generating the
Hail Caesars!
I received a 500 Internal Server Error when trying to create a new
page. Looking through the stack trace, the problem turned out to be
that there was no default page.status set in Radiant::Config. I set it
back to draft and all is well again.
Maybe it makes sense to default to
On 24 Jan 2011, at 06:32, Cleverlemming wrote:
Hail Caesars!
I received a 500 Internal Server Error when trying to create a new
page. Looking through the stack trace, the problem turned out to be
that there was no default page.status set in Radiant::Config. I set it
back to draft and all
On Sun, Jan 23, 2011 at 8:50 PM, William Ross w...@spanner.org wrote:
From a brief look it seems that the rss-reader extension disables all page
caching. It does this in a rather inadvisable way (by amending the Page
class itself rather than defining a specialist subclass) but since your site
