Forum Replies Created

Viewing 15 posts - 76 through 90 (of 113 total)
  • Author
    Posts
  • in reply to: Plugin vs. installing into theme #1221
    Marcus
    Member

    SOLVED

    In class-piklist.php LINE 136:
    In function add_plugin:
    self::$paths[$type] = $path;

    The path for the plugin folder was being pulled via dirname(dirname(__FILE__))
    Which on a local machine was producing the backwards ‘/’ which affected the paths throughout the code.
    So changed the line to:
    self::$paths[$type] = str_replace('/', '\\', $path);

    And all is good. Have to figure out a better way to load the proper path for the plugin than dirname(__FILE__) on a windows machine, as it always seem to cause problems.

    Hope it helps someone else who has as weird a configuration as mine.

    Marcus

    in reply to: Plugin vs. installing into theme #1220
    Marcus
    Member

    Thanks Steve. I changed that back from your original post, which fixed that previous problem but didn’t fix this one.

    But I’ve somewhat found the problem. (just haven’t fixed it)
    In file: class-piklist.php

    Line 153, part of the render() function: ($view is one of the passed arguments)
    If the plugin is inside the piklist folders:
    The $view var when var_dumped shows the relative path to the file (just the folders)
    'fields/show'

    If the plugin is within my plugin folder:
    The $view var, shows the full path to the file, including the file name itself.
    'C:/html/master/personal/ssgoverhaul/publichtml/pluginfoldername/addons/mae-weeks/parts/meta-boxes/weeks-test-metabox.php'

    So when $view is processed by the next part of the function:
    $_file = (path_is_absolute($view) ? $view : self::$paths[$_display] . '/parts/' . $view) . (strstr($view, '.php') ? '' : '.php');

    It makes an unreachable path for $_file

    Marcus

    in reply to: Plugin vs. installing into theme #1218
    Marcus
    Member

    Just thought I’d explain it a little better so there is no confusion.
    On a clean install of wordpress your default folders are:
    /wp-admin/
    /wp-content/
    /wp-includes/

    And inside /wp-content/ their are standard folders as well:
    /wp-content/plugins/
    etc.

    I changed my /wp-content/ folder to /anothername/
    and my /wp-content/plugins/ folder to /anothername/addons/
    for security and client reasons.

    So when I moved everything from /anothername/addons/piklist/parts/meta-boxes/ (which is working brilliantly)
    to /anothername/addons/mynewplugin/parts/meta-boxes/ (same folder structure as what you linked to above) I get the meta boxes, but none of the fields show up.

    So since I followed the correct pathing instructions as you linked to above, /plugin-folder/parts/meta-boxes/ I can only assume that it must be because of my changes to the /wp-admin/ folder name, and the /plugins/ folder name that this is happening. That’s just my guess. If it is correct, then somewhere the pathing is hardcoded or using an incorrect wp constant.

    Sorry for the confusion Steve.

    Marcus

    in reply to: Plugin vs. installing into theme #1217
    Marcus
    Member

    Steve I’m not disagreeing in fact I’ve done the folder structure exactly like you show. I’m saying in my config I’ve changed the name of my plugins folder not my plugin.

    I feel it not being named plugins is causing the problem. Unfortunately it has to be a nonstandard name.

    Marcus

    in reply to: Need Help: 2 Big Bugs found #1211
    Marcus
    Member

    Ok, corrected that one field (thanks for that) and retried it, but unfortunately, the radio and the checks still don’t keep state.

    Whats interesting is that the states are being recorded in the postmeta table.

    Marcus

    in reply to: Autosum field? #1210
    Marcus
    Member

    Haha, I didn’t even realize that either.

    Awesome.

    in reply to: Need Help: 2 Big Bugs found #1207
    Marcus
    Member

    Sorry Steve, should have posted it earlier.

    Here it is: (snipt hosted)

    http://snipt.org/Ajhaj5

    Marcus

    in reply to: Metaboxes on the public side. #1180
    Marcus
    Member

    I’ve created a specific registration page in admin. (site.com/home/register)
    Now I’m trying to bring over the custom metabox for that page and put it in the front end.
    Using:

    // Load necessary admin files
    include( ABSPATH . 'wp-admin/includes/template.php' );
    include( ABSPATH . 'wp-admin/includes/post.php' );
    // Add meta boxes
    do_action('add_meta_boxes', 'page', $post);
    do_action('add_meta_boxes_' . 'page', $post);
    // Show Meta Boxes
    do_meta_boxes( 'home/register', 'normal', $post );
    

    Taken from several sites that tout they can show meta boxes on the front end of a wordpress site.

    Only problem is, I don’t think piklist builds these for the front end, only built in admin.

    Am I right? Is there a way to build the piklist meta boxes in the front end?

    Thanks

    Marcus

    in reply to: [bug] add_more not working in settings. #1176
    Marcus
    Member

    Thanks Steve.

    Can’t wait to use piklist even more. Wish it made coffee.

    Marcus

    in reply to: [bug] add_more not working in settings. #1174
    Marcus
    Member

    If you want a solution (at least semi-permanent) that will make it work in firefox and keep it working in chrome, open up the /piklist/parts/js/piklist.js file.
    And edit lines 378 and 379 FROM:

                }),
                 .disableSelection();
    

    TO:

                });
                // .disableSelection();
    

    this will allow it to work in firefox and also in the the rest of them.

    Haven’t researched why disableSelection is doing that in firefox, but if I get some time later, I’ll check it out.

    Marcus

    in reply to: [bug] add_more not working in settings. #1173
    Marcus
    Member

    I can confirm this also, its a firefox bug. Has been around for a while.

    Marcus

    in reply to: Plugins Dir renamed: WP_PLUGIN_URL #1159
    Marcus
    Member

    Sorry Steve I should have been clearer. It was originally content_url();
    Old lines:

    content_url() . '/plugins/piklist/parts/js/jquery
    

    Which means the plugins path was hardcoded, if someone has changed the name of their plugins directory it wouldn’t work.

    Changed it to:

    WP_PLUGIN_URL . '/piklist/parts/js/jquery
    

    And everythings fine now.

    Things are great, using piklist and wordpress to help a private school redevelop their website, ecommerce, staffing, data storage infrastructure, reporting, marketing, etc. Should be a 4 year project, starting with an 8 month phase 1 contract.

    Very excited about this client. They want some pretty cutting edge stuff.

    Marcus

    in reply to: Widgets not showing #1000
    Marcus
    Member

    Since you are looking at it next week, could you please see about giving it the option to become its own widget (instead of being a drop down selection in the piklist widget), or included in the piklist widget. And if you can turn off the piklist widget if necessary.

    Thanks

    Marcus

    in reply to: Widgets not showing #970
    Marcus
    Member

    Having the same problem here.

    in reply to: Adding new roles. #954
    Marcus
    Member

    Well in all honesty, I’m a wordpress newbie.
    I’ve been in the internet development game for over 23 years, and am used to creating full web software packages for clients, but I found more and more clients wanting something like Drupal, Joomla but mostly wordpress.

    I am only now delving into creating wordpress themes from scratch and creating my own plugins, so most of this is new to me. But once I found piklist, I almost want it to do everything for me, so I have to kind of pull back the reins and realize sometimes I’m going to have to learn the basics before I can run. (which I never do anyways, and just start running)

    Such as creating roles. LOL I wish Piklist did everything so I could focus on building and less on coding, but I realize there are limits to everything.

    I look forward to the day, when I can create anything within wordpress from piklist API, but until then, I’ll have to learn the wordpress API first, and pull my hair out like all other good WP devs. 🙂

    I’ll post the code to the full width responsive slideshow later this week. Take care guys.

    Marcus

Viewing 15 posts - 76 through 90 (of 113 total)