New pgForm prerelease (0.9)  Bottom

Go to page 1 - 2 - 3 [+1]:

  • pgForm is a module for Zikula 1.x.x and Postnuke .764 that provides template based input forms for Pagesetter publications. It effectively bypasses part of Guppy.

    I would like to build the first release for the extension repository at the end of this week. Please submit tickets on all issues that you might have run into.

    More about pgForm here: http://code.zikula.org/dits/wiki/pgForm
    Get it here: http://code.zikula.o…rowser/trunk/pgForm

    Changelog:
    pgForm 0.1.1
    - first SVN commit
    - fixed incorrect validate-URL on any-upload in pgForm_user_new
    - fixed misspelled call to prototype validation function
    - implemented scribite integration [http://code.zikula.org/dits/ticket/18]
    - implemented modification of Pagesetter publications functionality (edit a publication)
    - slight rework of new publication functionality
    - created pgForm_editThis plugin [discussed in http://code.zikula.org/dits/ticket/21]
    - created custom example new and modify templates [http://code.zikula.org/dits/ticket/23]
    - take Pagesetter 'goback' and 'returnurl' if pgfromgoback and pgformreturnurl have not been specified [http://code.zikula.org/dits/ticket/21]
    - added set_ parameter passing [http://code.zikula.org/dits/ticket/20]
    - implemented language independend name, display name, and description [http://code.zikula.org/dits/ticket/25]
    - implemented dependency checking on Pagesetter and scribite [http://code.zikula.org/dits/ticket/26]
    - fixed missing pid in update fuction thanks to remmingtonshowdown [http://code.zikula.org/dits/ticket/24]
    - implemented missing pnvarprephtmldisplay modifiers in templates [http://code.zikula.org/dits/ticket/28]
    - changed pnvarprephtmldisplay modifiers to pnvarprepfordisplay, pnvarprephtmldisplay only escapes a subset
    - decided not to support custom Guppy plugins, unfortunately too flexible to translate in terms of input, database, validation, etcetera
    - enabled editing of offline publications through proper implementation of id/pid parsing
    - implemented n-m publication relations [http://code.zikula.org/dits/ticket/15]
    - removed some obsolete pnvarprepfordisplay modifiers on formatted dates
    - several XHTML compliancy fixes
    - removed some obsolete comments
    - fixed check for hidden relations
    - fixed double submission [http://code.zikula.org/dits/ticket/35]
    - added scribiteeditor and scribitetpl parameters to pass to scribite instances
    - fixed permission checking on modifying existing publication [http://code.zikula.org/dits/ticket/36]
    - differentiate on version of scribite using editorheader before version 3.0 and loader afterwards
    - updated version to 0.9
    pgForm 0.9
  • Thank for all your efforts doing such nice module :)
  • myths

    Thank for all your efforts doing such nice module :)


    It's a very big pleasure!
  • I'm juuuuust starting to get into pgform.
    Is there a way to display the delete button without the update button?

    What I'm looking to do is create a "delete this" link that pops up some "are you sure" text with a delete button.
  • dks

    I'm juuuuust starting to get into pgform.
    Is there a way to display the delete button without the update button?

    What I'm looking to do is create a "delete this" link that pops up some "are you sure" text with a delete button.


    The buttons shown are dependent on the workflow defined for the specific publication type in combination with the rights of the user viewing the from. To achieve what you want there are two possibilities:
    • create a custom workflow (refer to the Pagesetter workflow manual)
    • create a custom pgForm template.


    To create the custom pgForm please refer to http://code.zikula.org/dits/wiki/pgForm and http://code.zikula.o…FormCustomtemplates. If you don't come right please do come back in this thread.



    edited by: dits, Jun 21, 2009 - 04:19 PM
  • Quote

    What I'm looking to do is create a "delete this" link that pops up some "are you sure" text with a delete button.


    Of course!!

    The question is do you want this "delete this" button to be available from the "-full.html" template or form the pgForm edit template...

    That is, you can create a plugin to be used in the "full.html" template that displays the button and then a warning message and then runs the process to delete the publication (you needn't go through pgForm or guppy to do this- you just need to know the Pagesetter API to delete a publication)

    OR

    you can have this button available in the pgForm template that one sees after clicking "edit this" from the "-full.html" template... In this case you could hardcode the button into the pgFrom template and add some javascript to pop-up a warning message... but this method is a little long- if one wants to delete a publication the shouldn't have to go into the edit screen and then select to delete it... rather they should be able to go to the publication and simply delete it with one click...


    -J

    --
    Burnham Racing
    Illinois Cycling Association
  • when attempting to create a new document, I get the following:

    Code

    CalendarDateSelect Error: Prototype could not be found. Please make sure that your application's layout includes prototype.js (.g. <%= javascript_include_tag :defaults %>) *before* it includes calendar_date_select.js (.g. <%= calendar_date_select_includes %>).


    This is using .764
  • dks

    when attempting to create a new document, I get the following:

    Code

    CalendarDateSelect Error: Prototype could not be found. Please make sure that your application's layout includes prototype.js (.g. <%= javascript_include_tag :defaults %>) *before* it includes calendar_date_select.js (.g. <%= calendar_date_select_includes %>).


    This is using .764


    Thanks for reporting Darryl . I've created a ticket http://code.zikula.org/dits/ticket/40. Will look into asap.
  • Darryl,

    All my PN 764 sites have a javascript/ajax directory with prototype in, but it seems 764 originally did not ship with this directory. Does your's?
  • I have an original .764 release archive and it does have the javascript directory, but not the Ajax directory.

    I seem to remember that prototype was part of a separate archive that had to be installed on top of PN.

    Oh, for the record, I have been using the pre-release of pgForm in Zikula 1.1.1 and haven't run into any issues. Note, however, that I haven't been using relations yet.



    edited by: Wendell, Jul 01, 2009 - 06:44 AM
  • Thanks Wendell,

    Will commit solution for the Ajax tonight. Interesting signature BTW icon_biggrin
  • FYI - I did a little snooping to find the "Ajax Support Package" for 0.764 that I pulled from the depths of my memory and found it here: http://code.zikula.org/dizkus/downloads
  • Wendell

    FYI - I did a little snooping to find the "Ajax Support Package" for 0.764 that I pulled from the depths of my memory and found it here: http://code.zikula.org/dizkus/downloads


    Yep, found that one as well. It's got prototype 1.5.1 in though, the calendar requires 1.6.0 though icon_frown . So I included 1.6.0.3 for .764 icon_smile .
  • dks

    when attempting to create a new document, I get the following:

    Code

    CalendarDateSelect Error: Prototype could not be found. Please make sure that your application's layout includes prototype.js (.g. <%= javascript_include_tag :defaults %>) *before* it includes calendar_date_select.js (.g. <%= calendar_date_select_includes %>).


    This is using .764


    Should be fixed in latest SVN now.
  • banana

Go to page 1 - 2 - 3 [+1]:

This list is based on users active over the last 60 minutes.