Jump to content

karian

Members
  • Posts

    39
  • Joined

  • Last visited

Posts posted by karian

  1. After all that,  I still don't understand how the "https://www.../form-builder/?view_file=..." form builder url could end up being referenced by Google.

    It's an url generated by form builder, so it can't be crawled by Google bots (even in the situation in which "Files Path" is not configured correctly with a private folder)...

  2. Solved it by changing the hash functions in site/modules/FormBuilder/FormBuilderMain.php, thus invalidating old urls from working.

    A configuration for this hash could be exposed directly from the admin, useful to reset access to hundreds of files without erasing them.

  3. I realized we still need this form-builder special url access to share files among the team and non-admin members.

    A good solution would be the possibility to change the auto-generated url suffix (sequence of letters and numbers)...

    Looking into it.

  4. Hi everyone,

    Sending emails with WireMailSmtp works well but I would like to reflect sent emails on the email server "Sent" folder.

    Similar as what's discussed here. Someone mentions using imap_append ...

    Does anyone have a solution for WireMailSmtp?

  5. Hi,

    One of our clients, an art fair, uses the formbuilder plugin to gather applications from artists.

    Artists fill a form with a pdf of their work in order to apply.

    As one of the artists complained, the problem is that their file (managed by the formbuilder plugin) is public and referenced by Google.

    The url looks like "https://www.../form-builder/?view_file=...".

    Is there a way to protect the file or a least prevent it being referenced by Google ?

    Thanks !



     

  6. Hi everyone,

    I have a repeater inside a repeater (two nested levels).

    These repeaters are populated via the api.

      $page->of(false);
      for ($x = 0; $x <= 10; $x++) {
        // first level repeater item
        $repeaterItem = $page->repeater->getNew();
        for ($y = 0; $y <= 10; $y++) {
          // second level repeater item
          $nestedRepeaterItem = $repeaterItem->nestedRepeater->getNew();
          // edit item
          $nestedRepeaterItem->someField = "some datas";
          // save item
          $repeaterItem->save();
          // $nestedRepeaterItem->save();
          // $repeaterItem->nestedRepeater->add($nestedRepeaterItem);
        }
        // save item
        $repeaterItem->save();
        // $page->repeater->add($repeaterItem);
      }
      // save page
      $version->save();

    To obtain the expected result, I oddly had to use this command (twice) :

    $repeaterItem->save();

    Commented lines are what I thought would be right, but if I do I end up with several times the same repeater items.

    @Soma your example suggest:

    ...
    
    $item->save();
            
    // add the repeater item to the page
    $mypage->teasers->add($item);
    
    ...

    But it didn't work in the nested situation above, any idea why ?

    The only answer I see is that ->getNew() takes care of adding the item inside the repeater (maybe a recent addition to the api).

    Cheers

    • Like 1
×
×
  • Create New...