How to make editable description page attribute
Permalink 1 user found helpful
Hi, is it possible to make it editable the default description page attribute?
I mean, while creating a new page, I add the description there.
Then, on the page, while switching to edit mode, I would be able to edit the description text.
Is it possible?
I mean, while creating a new page, I add the description there.
Then, on the page, while switching to edit mode, I would be able to edit the description text.
Is it possible?
It's in the page properties (hover over the "edit page" toolbar button and click "Properties". (Or if you're on Concrete5.4, click on "Edit Page" then click the "Properties" button in the toolbar).
Hi Jordan,
first of all, I would like to thank you for your website that is full of invaluable resources about Concrete5, and of course, for you help here on the forum. You rock.
About the thread, I just think I got the wrong approach in designing the page type I need in a custom theme I am making.
I need a "screenshot image" and a "tagline" for a product page and then, a "product description". Of course, the "product description" will need rich text editing so, using the default "page description" is just wrong since I cannot use html tags or any other fancy stuff in it, isn't it?
So, should I use the description only for its related meta element?
Btw, since I got "you" :)
Is it right to use page attributes for tagline and screenshot?
I thought this way I have total control upon the code, forcing the user to fill them out and not needing to create custom blocks only for them. What do you think about?
And, again, really really thanks a lot for your time.
first of all, I would like to thank you for your website that is full of invaluable resources about Concrete5, and of course, for you help here on the forum. You rock.
About the thread, I just think I got the wrong approach in designing the page type I need in a custom theme I am making.
I need a "screenshot image" and a "tagline" for a product page and then, a "product description". Of course, the "product description" will need rich text editing so, using the default "page description" is just wrong since I cannot use html tags or any other fancy stuff in it, isn't it?
So, should I use the description only for its related meta element?
Btw, since I got "you" :)
Is it right to use page attributes for tagline and screenshot?
I thought this way I have total control upon the code, forcing the user to fill them out and not needing to create custom blocks only for them. What do you think about?
And, again, really really thanks a lot for your time.
Thanks for the kind words, you're very welcome.
I rarely use the built-in "description" attribute (I really wish there were an option to hide it all the time because it just makes everything confusing for my clients). Instead just create my own attributes. You can create your own attribute of the "Text Area" type, and choose one of the "Rich Text" settings to give it a WYSIWYG editor.
As for your question about if it's right to use attributes... my philosophy is that the most important thing is avoiding duplicate data entry for your users. So if the screenshot and tagline will appear in the page itself, it should stay in the page content (and then use something like the Page List Teasers addon or custom block or page list code to pull that out of the page when you want to show it in the top-level index page). BUT if it's something that will *not* appear in the page itself (that is, if the tagline and screenshot will *only* be shown in the top-level index), then it should be in an attribute.
Hope that makes sense.
-Jordan
I rarely use the built-in "description" attribute (I really wish there were an option to hide it all the time because it just makes everything confusing for my clients). Instead just create my own attributes. You can create your own attribute of the "Text Area" type, and choose one of the "Rich Text" settings to give it a WYSIWYG editor.
As for your question about if it's right to use attributes... my philosophy is that the most important thing is avoiding duplicate data entry for your users. So if the screenshot and tagline will appear in the page itself, it should stay in the page content (and then use something like the Page List Teasers addon or custom block or page list code to pull that out of the page when you want to show it in the top-level index page). BUT if it's something that will *not* appear in the page itself (that is, if the tagline and screenshot will *only* be shown in the top-level index), then it should be in an attribute.
Hope that makes sense.
-Jordan
Thanks a lot, it does make sense.
Essentially, custom page attributes if you need to use them in different places (such as index pages, page lists, etc.) and just page content if you need to use it just on that specific page, right?
Thank again,
Giuseppe
Essentially, custom page attributes if you need to use them in different places (such as index pages, page lists, etc.) and just page content if you need to use it just on that specific page, right?
Thank again,
Giuseppe
Correct.
Unless it's on the page content *and* in page lists / index pages -- then you either want to use the custom attribute and display the custom attribute values in the page type template, or keep it in the page content, and use some custom code to retrieve those content blocks from the page itself. (The free "Page List Teasers" addon is useful for this, if you don't want to write any php code).
Unless it's on the page content *and* in page lists / index pages -- then you either want to use the custom attribute and display the custom attribute values in the page type template, or keep it in the page content, and use some custom code to retrieve those content blocks from the page itself. (The free "Page List Teasers" addon is useful for this, if you don't want to write any php code).
