page part forms (custom fields)
|
70 posts
|
@andydtwo formatting the date is not ppf specific. It’s managed by the Frog datapicker applet. I doubt that you can change it to a different format (yet). The only thing I see is to issue a change request to the Frog core. M |
|
17 posts
|
Hi! This is very handy plugin! Thank you for bring it to the Frog! I have 2 questions. 1. Will you support this plugin in future frog releases? |
|
70 posts
|
@zigmat
Currently I’m working on some bugfixes and enhancements. So the answer is yes as far as this is possible.
I don’t know about Frog, but at the ‘forked sister project’ Wolf CMS there are some discussions right now to add this (with better support) to the core. |
|
108 posts
|
Is there anyway then just to change the date to a UK format from the american format on the frontend when calling it to a page? I have my client entering in a portfolio date and this needs to be reformatted on the frontend…it doesnt matter he picks it in american in the backend but it would be nice to format it correctly on the frontend. |
|
70 posts
|
@andytwo
What about: |
|
108 posts
|
Thanks M. I should have figured that one out. I always think its more complicated than it is. Cheers for your help. |
|
184 posts
|
Hmmm, I keep getting “Page part form not found” when I try to save one … |
|
108 posts
|
make sure this line is exactly as is in your config file: |
|
184 posts
|
I did that first, funnily enough. That ain’t doing it for me. Debug isn’t giving me anything either … |
|
108 posts
|
Have you got true in there as well? As apposed to |
|
184 posts
|
Yep, I have true defined. Perhaps there is a table expected in the database that hasn’t been created? |
|
108 posts
|
Did you follow all the steps in the previous detailed stages? Edit the particular files e.t.c? If you have just double check! |
|
184 posts
|
Yes. 1. Latest jQuery plugin installed |
|
184 posts
|
Looking at the plugin setup script, it appears that there should be a PagePartForm table. Can anyone confirm if they have one created? As I don’t see one. |
|
108 posts
|
Make sure the tables exist in your database and deactivate and reactivate the plugins. |
|
184 posts
|
It was a rookie mistake on my part … the table wasn’t created because I installed the plugin ‘BEFORE’ the metadata plugin. All working now … for anyone else, be sure that the Metadata plugin is installed PRIOR to PagePartForms plugin to ensure the PagePartForm table is created. |
|
108 posts
|
Cool, glad you’re sorted. |
|
184 posts
|
Me too. Thanks Andy. |
|
184 posts
|
I’ve started using this plugin as an addressbook of sorts. Thus far I have created a parent archive under which all the people will be created in and have created the first page (person) with desireed page parts from selected (it has a title, firstname and surname) which displays above the body textarea for my first entry. But, as I create additional people pages in the archive, the tabs appear but not in the same place (it seems that additional pages must manually select the page part form, for the layout of those page parts to inherit the page part layout – which makes sense of course). Is there a way around this though? otherwise, I’m thinking of creating the desired fields first, then disabling the page part forms to avoid the page part form having to be selected for each person page (afterall, having created the first page, each page already inherits the page parts – just not with the format of the page part forms). |
|
108 posts
|
I wondered this as well…it should inherit the parent level or the first in the list maybe better, leaving the parent to do whatever….dunno, just an idea. |
|
1 posts
|
I’ve modified the plugin to allow inherited page part forms. This modification creates an additional field for each post, called “Page part form (for children)”, which allows separate control of all children of a page (it doesn’t affect the page part forms of the current page). The change is here: I don’t recommend using it until it’s integrated back into the original plugin (which I hope will happen soon). -bill |
|
108 posts
|
Thanks for the contribution billzeller! |
|
4 posts
|
I have small problem. When I use Multi-select List Box, chosen values are saving in database like this: ? |
|
184 posts
|
Hey billzeller, Thanks for that. Perhaps I’m missing something, but if I select a ‘Page part form (for children)’ in a parent page then create child pages, the Page part form does not inherit from the parent … it must still be manually selected. Are there special circumstances in which the inheritance works? Edit: Forget what I said, I had literally taken the download ‘as is’. Applying your changes to the callback_view_page funtion got it working: http://github.com/billzeller/frog_page_part_forms/commit/b0d6226afea970a80d814ad46e534b8e92a6369e |
|
184 posts
|
Has anyone successfully changed the styling of a textarea generated by page_part_forms? I’m having trouble finding what is overriding my width values. Edit: For some reason it is overriden by an inline width of 100%. To rectify this, you just need to remove the style attribute from line 117 in /views/observers/page_form.php … you can then use the stylesheet to style the textarea. |