Forum Replies Created

Viewing 15 posts - 1 through 15 (of 16 total)
  • Author
    Posts
  • in reply to: Maintain State Between Workflow Tabs #1290

    Thanks so much for the reply Marcus.

    I think what I will try for now is just to add a “Save” button to the bottom of each workflow page. That way at a draft will be saved.

    It would be great if a pop up dialog would come up if a user clicks on a new tab and has not saved their work on the current page.

    Ideally I would like the post to save automatically as a draft each time a workflow button is clicked and I’ll continue to look into it.

    One thing I have noticed is that if the user doesn’t save/publish the post before clicking another workflow tab then a new auto-draft of the post is entered into the database which can cause some bloat.

    Cheers,
    John.

    in reply to: Project status? #1278

    I would also donate!

    in reply to: Limit add_more #1273

    +1

    Thank you!

    in reply to: Created New Field (Heirarchical Taxonomy Select List) #1272

    Hey Marcus,

    Could you share the code that displays the select field for your Heirarchical Taxonomy Select List?

    Thanks!

    in reply to: Tabs On Edit Pages #756

    +1

    in reply to: Custom Status Trouble #742

    @steve – Thanks.  I’m still having a little trouble with custom status.  If I have PikList Demos enabled I can set custom status and they show up in the publish metabox on edit pages.  However, if I disable PikList Demos the custom status disappear on my CPTs.

    Can you think of any reason for this?  I can send code if you need.

    Thanks!

    in reply to: Custom Status Trouble #729

    OK, I figured out what my problem was.

    I didn’t realise that it was possible to set custom labels for a CPT registered with PikList so I was using a custom array like so:

    function report_post_type($post_types) {
    $labels = array(
    ‘name’ => (‘some-label’),
    );

    $post_types[‘report’] = array(
    ‘labels’ => $labels

    Then I realized that you could set custom labels a-la this thread:

    http://piklist.com/support/reply/reply-to-setting-labels-on-new-type/

    So once I set the labels using the ‘labels’ array within the $post-types array then I could set custom post status’

    in reply to: Set PikList to use https:// #695

    The other two places that I hardcoded the URL were:

    class-piklist-theme.php line 42

    class-piklist-form.php lines 249 & 250

    That removed all of the errors for me.

    Functions are:

    wp_register_style

    wp_register_script

    wp_enqueue_script

    wp_enqueue_style

    in reply to: Set PikList to use https:// #694

    Thanks Steve.  I am getting these errors in Chrome’s javascript debugging console:

    [blocked] The page at https://www.MYSITE.com/wp-admin/post-new.php?post_type=book ran insecure content from http://www.MYSITE.com/wp-content/plugins/piklist/parts/js/pik-admin.js?ver=0.1.
    [blocked] The page at https://www.MYSITE.com/wp-admin/post-new.php?post_type=book ran insecure content from http://www.MYSITE.com/wp-content/plugins/piklist/parts/js/pik.js?ver=0.1.

    If I go into the class-piklist-admin.php file on line 232 and change the WP_PLUGIN_URL to a hardcoded URL with an HTTPS:// prefix that removes the errors. But, of course, this will get over written in an update.

    Same on lines 242 and 243 of class-piklist-admin.php.

    It looks like when PikList is enqueing scripts and styles is when the issue occurs.

    in reply to: Lock field on multiple post status #680

    Here is a pastebin of my code if that helps:

    http://pastebin.com/aHh9p2km

    Thanks,

    John.

    in reply to: Lock field on multiple post status #679

    Thanks Steve.  That makes sense.  However, no matter what I try I cannot get this to apply to more than the first status.  Which ever status I list first is the only one that is recognized.  Does the status have to be a custom status defined in the CPT parameters?

    I am using WP 3.5.1 and PikList 0.7.1

    I’m stumped.

    Thanks.

    in reply to: Setting Url of admin menu for CPT #628

    @steve.  Thanks for the suggestion.  I will think this though a little more.  My solution so far has been to do the following:

    1) I registered a CPT via PikList and left the show_ui parameter to true.

    2) Via a separate add_menu_page function I added a top level menu and set the capability of that menu to “Author”.  So authors will see that menu.  I set the plug parameter to the page that I wanted.

    3) Then, with the Adminimize plugin I turned off the top level menu for authors.

    The result is that the menu created with add_menu_page does not show to admins at all.  The default UI menu created by registering a CPT with PikList shows to Authors and Admins but the menu is hidden to Authors via Adminimize.

    This seems to work for now.  Thanks a lot for the replies.  I can’t wait to see what is next for PikList!

     

    in reply to: Setting Url of admin menu for CPT #621

    Hi Steve,

    Thanks for the response.  I’ll attempt to explain.

    I am using the Adminimize plugin to control menus and other aspects of the admin UI for roles other than Admin.  I have a CPT registered as “report”.  For non-admins I have hidden this top level menu because I don’t want them to be able to get to the edit.php page for that CPT.

    Via PikList I have created a sub-menu page for this CPT.  Because there is a submenu, the top level menu then has to be shown. It looks like Adminimize is rewriting the link on that top level but the link is not what I want.  Here are the two links:

    Top Level: MYSITE/wp-admin/admin.php?page=royalty-report-list

    Sub-menu: MYSITE/wp-admin/edit.php?post_type=report&page=royalty-report-list

    These two links are producing different query results.  I know that there are a lot of variables here and it’s difficult to see what’s happening if you can’t see the code.  What I would really like to do is just set the link on the top level menu so that it points to the correct URL.

    Thanks again and let me know if you would like login creds and I can send them to you so you could look at it.

    in reply to: Make a field "Read-only" #614

    @steve – Thanks!

    in reply to: Best code practice for field description #611

    Never mind.  I just found the localized text explanation in the documentation:

    http://piklist.com/user-guide/docs/fields/field-parameters/

    Thanks!

Viewing 15 posts - 1 through 15 (of 16 total)