addedValues Plugin

...Powerful Free! Database Expansion for Manila
logoBottle:

(1 or more words)


Get tropes here!
Click to see internals
Report bug


FemNet

sitepic_femnetscreenshot.gif:
Viewable with Any Browser

Members
Join Now
Login

How to create the simplest addedValue site

In this example we create single variable called pagelabel and use it as a meta variable. Since this is the first and easiest example , we take it step by step in great detail. Click on any of the small images to view a full size version.

We start with a new empty Manila website, creating it from the controlpanel (new in Frontier 9.0). If you don't have access to the admin website, or some other way to create a new site, you will have to have your server administrator do it for you. pic_howto1_img1:
Success. We have to log on before the next step. pic_howto1_img2:
The Managing Editor must enable the addedValues plugin in each new site pic_howto1_img3:
Click on the Editors only menu link to addedValues to get to the home page of addedValues. pic_howto1_img4:
First thing to do is to declare one variable.
Choose the Variables menu item from the left navigation.
Once on the variables page we add a new variable called pageLabel. This means we could store a value called pageLabel in each message in the discussion group.
pic_howto1_img5:
Success! Now we look at the properties or attributes of the variable. pic_howto1_img6:
Lots of possibilties here.
Notice the links to help in the left most column.

Let's change just 2 properties - allow pagelabel to be edited by Members (the default is Managing Editors only) and we set As META in <HEAD> to Yes.
pic_howto1_img7:
Next step is to instruct addedValues to add a way to enter and modify values for pageLabel when we create or edit a message. So we go to the forms page in addedValues. We want to create a form, it will be for messages and will be used insteads of Manila's form when the user clicks the ETP (Edit this Page) button.
Fill the fields and click Add.
pic_howto1_img8:
The response is a formidable looking page, best understood as 3 stages in customising a form .
The first section controls what variables, of all those eligible, we wish to enter from this form. We don't have a large choice here and addedValues has done the sensible thing for us, so we move on without changing anything.
pic_howto1_img9:
The second section of the form deals with how each new field we add will appear in the form. Typically there are just a few alternatives for each variable, with some parameters you can tweak such as width of a field or the number of rows, for other variables there can be as many as 6 or 7 different renderings. addedValues tries very hard to show you what the different alternatives would look like in the form. Again addedValues has chosen pretty sensible defaults. It may want to make a WYSIWYG field out of pageLabel, if so turn that off and click Set Rendering. Otherwise move on. pic_howto1_img10:
The last part of setting up your form is the layout or look and feel. Make it as fancy as you like. Just keep in mind that In an ETP form, Manila expects to see just 2 fields subject and body, you must provide them. There are many ways to deal with this requirement, the simplest is to emulate how Manila does it. The textbox pseudo-macro exists soley to cater to this need, read the page help for details. Click Set layout pic_howto1_img11:
To see if the layout is what you had in mind, Click the link above the layout box.

You see a rendering of your form, where you can enter and modify test data. Nothing changes in discussion group messages, your input is stored in a private data area reserved for this form and only used for test purposes.
pic_howto1_img12:
Fill in the form, test the data validation, if you enabled any.

Tweak the layout and try the form again - this is your development environment, so make use of it.
When finished click the Done button.
pic_howto1_img13:
Before this form will be used by Manila, you have to tell addedValues to override the default forms. We will do this only for stories for this example.

Click the Configure button to override Manila ETP forms for stories.
pic_howto1_img14:
Choose Stories from the editors only menu.
Click on Create a New story.
pic_howto1_img15:
Recognise the form you made?

Fill in some data, be sure to add something to the pageLabel field. Post the story.
pic_howto1_img16:
Manila accepts the story, but how do we know it worked?

Look at the page source in your browser.
pic_howto1_img17:
You should see at least the meta tag in this picture. Manila now seems to know about pageLabel. Congratulations, the mission is complete. pic_howto1_img18:
It's a little annoying that we have to view source to see if we stored a value in the story. For extra credit, let's do this another way...
Edit the page again, and add a macro call to retrieve the value using an addedValues macro. Read more about "addedValue Macros" in the Reference section of this site
pic_howto1_img19:
And there we have it. pic_howto1_img20: