Jump to content

tpr

Members
 View Profile  See their activity

  • Posts

    2,321

  • Joined

  • Last visited

  • Days Won

    44

 Content Type 

Everything posted by tpr

  1. tpr
    I've added a few fields to Language pages (language_code, language_locale, etc) and it seems that textformatters have no effect. I solved the issue in other ways (which is much better), but curious to know if this is by design or a bug.
  2. tpr
    Why don't you create separate pages instead? That would simplify things a lot, now and later.
  3. tpr
    Thanks guys, could've asked earlier to save some time Finally I settled with this: $templates->get('package')->fields->getFieldContext('body')->$labelLang Where $labelLang is 'label' + language ID (if it's not the default language, otherwise simply 'label').
  4. tpr
    I try to re-use fields and would like to display the field label on the frontend, but all I got is the default label, not the overriden one. It's a multilanguage site but I don't think it matters. This is what I've tried: echo $page->fields->body->label; echo $templates->get('package')->fields->body->label; Is there a way to get the overriden label text?
  5. tpr
    That's still an error even if it's gone. I'm in a pw 305 project but haven't notice this, will check later again. Thanks for the info.
  6. tpr
    That's good news - I tried to replicate the bug you mentioned in PW 2.7, so I guess that's not the PW version that solved it.
  7. tpr
    Looks great, thanks! Those preview images always remembers me of pox
  8. tpr
    Yes there are, but they don't have time to do everything
  9. tpr
    I have version 1.2.0 and I couldn't reproduce:
  10. tpr
    Create a form, set its action to URL where you process the submitted values (here bootstrap PW and save a new page). Then redirect. You may hardcode form inputs if they don't change often, or pull directly from the given PW age. I guess you have to manually manage autocompletes and selects.
  11. tpr
    Maybe you have set access rights for the title field?
  12. tpr
    PW is different because updates are mostly installed by devs who finished their projects much before deadline and would like to have some extra fun time in the admin
  13. tpr
    If you save your pages under the Admin section in the Page list, isn't that OK to you?
  14. tpr
    I'm talking about the same thing. In the video above, you should set the second select's "News" option selected (php), and set "container" as the value of the first input (also in php). These variables (IDs) should be present in POST/GET. Once you manage to populate these two, trigger the 'change' event to get the third select.
  15. tpr
    Yep, just set the first two selects' value using php (POST/GET), and then your toggleFields function in document ready should do the rest. Edit: of course you should trigger the 'change' event to make it work, e.g in the end of document.ready function $('#type').trigger('change');
  16. tpr
    I would simply sort pages by title, and echo the first letter only if it's different from the previous.
  17. tpr
    So the third select is generated on the fly, so it's not on the page if previous selects are empty? If so, you may trigger a 'change' event for the second select (using the POST/GET variables, if the exist), and this should create the third select. Basically it's the same as if a user had entered something to the second select.
  18. tpr
    Populate the two selects with PHP using POST or GET variables (according to your form's method).
  19. tpr
    A dummy button for sorting items with JavaScript wouldn't work? Then use the default save button to save the page. This could be automatized adding a Js event to the save button.
  20. tpr
    This is great, thanks! Also seems to honor "Branch edit exclusions" so it's even better. Just a side note: my current setup has identical page names so a few pages come up twice, but that's because of my custom path hook. However, this is only a cosmetic issue as those paths are the same, selecting any of those is OK.
  21. tpr
    Thanks! I can't try it atm but will as soon as I will have a pw3 project
  22. tpr
    This improvement could come handy, for me it comes up regularly. API method to check if image is a default image: would return true if selecting a page instead uploading an image, using the admin "Default value (when empty)" field (eg. "isDefaultValue" or "isPlaceholder"). Currently I have to check for a file name ("no-image.png"), obviously not the best way.
  23. tpr
    Massive update! As for field templates, how about distinguishing them by templates? For example: body.php for all templates, body-home.php for body field for home template, body-contact.php for th contact template?
  24. tpr
    Nice module! I would love to see a feature to allow adding unlimited votes using the api without binding to a user. So for example to put a review form on the site where people (not users!) could vote. Their submitted votes would be processed then using the add() method. Currently it doesn't work because once you use add(), you cannot add another vote with the same user. Commenting out the body of the current() method in the module seems to work, but an official solution would be nice.
  25. tpr
    I guess you're aware of that inserting links using the autocomplete field in the CKEditor lists pages outside the restricted branch. Is there anything that can be done here? For me it's OK to only hide the autocomplete field for now.
×
×
  • Create New...