On Tue, Jun 2, 2009 at 5:02 PM, Charlie Robbins
charlie.robb...@gmail.comwrote:
The edit published_at field is disabled by default in the Admin interface.
You can enable it by changing a config value.
Radiant::Config['page.edit.published_date?'] = true
More on the wiki:
These extensions seem to be related and both fail in the same way.
Click on products and I get: 500 Internal Server Error. Is this a
problem with the extension not being updated to run on 7.1 or am I
missing something about the install process? They both seem really
cool and I'd really
Vassilis Rizopoulos wrote:
On Tue, Jun 2, 2009 at 5:02 PM, Charlie Robbins
charlie.robb...@gmail.comwrote:
The edit published_at field is disabled by default in the Admin interface.
You can enable it by changing a config value.
Radiant::Config['page.edit.published_date?'] = true
More on
Vassilis Rizopoulos wrote:
On Tue, Jun 2, 2009 at 5:02 PM, Charlie Robbins
charlie.robb...@gmail.comwrote:
The edit published_at field is disabled by default in the Admin interface.
You can enable it by changing a config value.
Radiant::Config['page.edit.published_date?'] = true
More on
What I would like to do is specify a default part of a page that would
have a default banner, but I would like to override that on some of my
pages. It would be great if something like this worked:
r:if_content part=topBanner
r:content part=topBanner /
r:else_content
img
Unfortunately, no. But you can use the converse, r:unless_content to
accomplish the same thing as the else.
Sean
N. Turnage wrote:
What I would like to do is specify a default part of a page that would
have a default banner, but I would like to override that on some of my
pages. It would be
