[pmwiki-devel] Accessing new page attributes / property
pmwiki at solidgone.com
Sat Jan 3 11:39:27 CST 2009
Petko Yotov wrote:
> Currently, it should be much easier to use a custom Cookbook:MarkupExpressions
> function do display similar properties of each page.
Not sure I follow your meaning here. Are you suggesting using a ME in
place of the $FmtPV page-variable? If so, what advantages are there?
> I feel in most cases it would be simpler/wiser/easier to store such
> information in PageTextVariables or MarkupExpressions, or custom markup, that
> all could be manually edited in the page, and not in a PageAttribute.
I'm storing all other info in PTV's -- but this one attribute I need to
protect from being edited. The PTV's are being entered via a PmForm. My
assumption (not yet tested) was that if someone has privs to initially
create a data page from the PmForm, then they have privs to subsequently
edit that page -- there's no way to say allow create but not edit. Thus,
putting the value in a page attribute.
> store such information in PageTextVariables or MarkupExpressions,
> or custom markup,
Related to the first point, I'm not clear how to store data in a
MarkupExpression. I can see how to access/display data using the markup,
but not store it. Perhaps I'm misunderstanding.
> Also check if the hardcoded sort function for the page array is not
> placing your attribute at the bottom of the actual file (function
> CmpPageAttr() -- called from class PageStore, function write).
The new attribute is stored near the top of the file.
More information about the pmwiki-devel