Jump to content

kongondo

PW-Moderators
  • Posts

    7,374
  • Joined

  • Last visited

  • Days Won

    139

Posts posted by kongondo

  1. I'm not sure which bit ticked me off more:
     

    1. bad to extend with modules and functionalities
    2. It is also not very object oriented 
    3. It does not have an ORM but offers a way to do query for custom fields/content blocks using a jQuery like syntax

     
    1. Really...seriously?
    2. All of PW is classes [OOP]. What does this mean ->
    3. Please...
     
    And why would we want this?

    If ProcessWire is rewritten with one of the popular frameworks, it would be really great

  2. .............a webapp where users interact with it by create, read update and delete data (CRUD).....

    What do you mean exactly by a webapp? As for CRUD, are you talking about this in the frontend then? Are you talking about a members only type of site, where you have to log in to edit your own page. Are you talking a social network site?....CRUD is possible but difficult to give you a more concrete answer unless we know the use case.  

  3. That's what I said...that tutorial is not really what you want...it was a btw...Dynamic population of dropdown lists is another matter altogether which I haven't the faintest clue about (i.e. in the Admin) save for that  it will require some Ajax...:-). Sorry, I can't be of help...

  4. What  is the point of restricting the use of a template for new pages if after the page is created any template can be assigned to it via edit > settings?

    Surely this is not the way it is supposed to work or am I missing something here?

    I agree. Like I said, for the "no children" allowed setting, it works just fine; no children can be created using "new" in tree and the children tab is hidden when editing pages using that template. Likewise, logically, I would have thought that the template setting ..."no new pages" aka "parents" would be respected throughout...Unless there is some other thinking Ryan had? But, look at his is comment in the code in the Class Template:

    'noParents' => '',   // set to 1 to cancel use of parentTemplates

    I'm going to test with older versions of PW to see what the behaviour was then...or have you tested?

  5. Do you mean when you create a new page you can use the sitemap template when creating or use it when editing the settings?

    1. Create a page: sitemap will not be available in the templates drop down - which is expected due to Template Family restriction (no new pages)

    2. Edit the new page:  sitemap is available under "settings". OK, so I thought I'd get an error if I tried to change the template to sitemap but nada! I am able to do it

    I have also tested with search template...

    The only Family restriction working fine is "no children"

  6. OK, edit...this is now strange..

    When editing the pages (like Dazzyweb said), I can now see all the other restricted templates as well (under settings) and I can even assign them to this page! For instance, the template "sitemap" has family restrictions: "no children" and "no new pages", yet, I am able to assign new pages to this template! What gives?! Uh?

    Just to clarify...the "no children" bit is working fine; I cannot add children...either via the tree or in children when editing the page since "children" is not visible...So working fine

×
×
  • Create New...