fenton

... the only setting that is different would be the hidden parent

thanks LostKobrakai,

so having 9 different templates with 9 different PageTable fields wouldn't be something too weird, then ...just checking in to find the right approach

Repeaters aren't ideal in this case, because the pages will have quite a few data entries

Hi there,

I got a section on a site (9 pages) which uses a PageTable field to enter a datagrid for each page.

my first approach was to create a  template with a specific PageTable field for each of the 9 pages, so that I can select a hidden Parent page ...this worked, but got kinda messy.

Now I reverted back to only one template, one PageTable field and the children listed below each item. Looking at it now I think it will totally confuse the editor, since every other child page to edit for him is a "real" page, ...so I'm trying to find a way to hide these children or create them in a hidden folder, but render them according to the corresponding page where it was created from

does anyone know how to tackle this or has an alternative way to do it? (it's a multi language site, so I can't use the table field)

thanks a lot, cheers, j

great module! thanks David

... oi

changed access for the template containing the PageTable pages to "guest (everyone) -> view pages"

Hi there,

I got multiple PageTable fields with their parent containers placed within the "admin" area of the site tree. As I found out just now, I'm only able to see the output on the frontend when I'm logged in.

any ideas how I can fix this?

thanks a lot, cheers, j

Isn't that the same with the PageTable Field? I mean, entries are saved as subpages
 

Overhead means that repeaters are actually pages, which are stored somewhere in the admin section. But it's not the pages per se, but it should be something about the handling of them as I remember Ryan stating that pagetables are better in that regard.

weird, seems to work now

any ideas about the unpublished state when publishing?

thanks, LostKobrakai! ...it worked

any ideas about the unpublished state when publishing?

Hi there,

like the title says:

my PageTable Field entries stay unpublished until I manually untick the "unpublished" checkox. Clicking on Publish won't do it.

does anyone experience the same or does anyone know how to solve it? (btw. the Child Pages are in a folder within the Admin area of the site)

.... another question: is there a way to hide the Title Field? The Title is generated automatically, so it might be confusing for the editor

thanks a lot, cheers, j

okay, for the Submit Button I was able to translate the string on line 148 with:

$submit->value = __("Senden");

http://processwire.com/api/multi-language-support/code-i18n/

Hi tpr,

thanks

that's what I was assuming, but at the moment I have no idea how to alter the generated form markup

more important actually for me atm is how to make the send button multi lang

as I see it, the Submit button is added here (FormTemplateProcessor.module):

        // the inputfields don't already have a submit button, so we'll add one.
        $submit = $this->modules->get("InputfieldSubmit");

        // set a random name to the submit button so that this form doesn't process
        // any submissions without first receiving a rendered form. This isn't
        // necessary, but it may help to reduce automated spam to the form.
        $submit->name = "submit";
        $submit->value = 'Submit';

        // add the submit button the the form
        $form->add($submit);

... me again

using Adrian's Module now https://processwire.com/talk/topic/59-module-want-form-builder/page-5#entry41431 and it works great

just wondering how the Form Markup is generated? I assume that's an internal PW Function right, since it's based on jQuery UI & uses FontAwesome

any ideas how to make the Send Button text or Tooltip notification translateable for a multi language page set-up? ...or how to alter the generated Markup, so that it's not a Tooltip but displayed like an error message like for an empty field instead?

thanks a lot, cheers, j

btw. where's the JS Tooltip coming from anyways? haven't included jQuery UI in the frontend

Hi LostKobrakai,

thanks a lot

sorry, I know ...this "Profield: Table thread" got hijacked a few pages back

in my case, I can't use the "Profield: Table" option, because it doesn't have multi language support. will see if changing the parent will be sufficient for my setup for now.

cheers, j

1. how can I display Multi Language Strings e.g. __("Your Name") in the rendered form?

okay, found a solution for this, just assigned __("Your Name") to a variable like $name = __("Your Name") and placed the variable in the form markup

... now trying to find a solution for the Umlaut problem

Hi there,

1. is there an option to hide child pages of a PageTable field from the tree other than having another parent?

2. is it possible to have child pages set to "hidden" by default somehow?

thanks a lot, cheers, j

Hey Marty,

just checked again and it seems to work

not sure what I changed though, 'name format for children' was left blank all the time.

Hi there,

I got two questions regarding Ryan's Form: https://processwire.com/talk/topic/59-module-want-form-builder/page-3#entry8457

1. how can I display Multi Language Strings e.g. __("Your Name") in the rendered form?

// output the form
            echo <<< _OUT

            $error
            <form action="./" method="post">
            <label for="fullname">__("Your Name")</label><br />

            ....
</form>
_OUT;

2. I'd like to send Umlauts, right now they don't get sent properly "ÃÀÌ" etc. I see someone had a similar problem (https://processwire.com/talk/topic/59-module-want-form-builder/page-5#entry59150) but checking Ryan's code it should work already properly:

// encode values for placement in markup
            foreach($form as $key => $value) {
                $form[$key] = htmlentities($value, ENT_QUOTES, "UTF-8");
            }

thanks a lot, cheers, j

does anyone got this with a multi-language setup working?

thanks,

hmmm, damn ...might be

I haven't used this with a multi-language setup either so I'm not sure if that has anything to do with it.

my date field is set up like this:

thanks, Marty

created a new template as container for month & year and it seems to work, although the urls look like this:

any ideas? how is your date field set up?

cheers, j

hey Marty,

yes, should it be a different template?

Hi there,

anyone got this module working with PW 2.6.0?

everytime I create a new page with the template "article" under "News", my "News" container (and any other published page on the first level) will be deleted and replaced with the new container "2015"?

anyone experience something similar or know how to fix it ...maybe even a similar, up-to-date module for the same task?

thanks Wanze!

great, thanks, hdesigns! will check them out