Forum Replies Created
-
Posts
-
@ehoanshelt– Think of each input row as a grid system with 12 columns. You want OPEN to be 6 columns and CLOSED to be 6 columns.
See if this code works: http://pastebin.com/0AwZbQqw
@mikel– We’re working on getting rid of them. Should have an update this week. Thanks for being patient.
@ehoanshelt– There seems to be a bug with disabling add-ons. If you want to delete it now, you can just remove this directory in the PIKLIST plugin:
/plugins/piklist/add-ons/piklist-demosWe will try to fix this quickly.
These look like PHP notices, which we are working on. Check out this thread and see if they go away: http://piklist.com/support/topic/new-install-w-errors/
@ehoanshelt– This is a little confusing and definitely needs a tutorial… which we will write up this week.
You can try this code, which I reformatted a bit to make it easier to explain:http://pastebin.com/RCaFUdcP
Essentially you can use any of the parameters in the WordPress get_terms function. The reason nothing was showing up was probably because no posts (or CPT’s) were actually assigned as a “specialty”. By default get_terms only shows taxonomies that have content assigned to it.
By setting “hide_empty” => 0, you told WordPress to pull all the taxonomy values for “specialty”, regardless if they have content assigned or not.
Try out that code and let us know if it works.
@mikel– We’re working hard to fix all the PHP notices in Piklist and should have a fix for you this week. Temporarily you can turn off your notices by adding this code to wp-config.php:
@ini_set('display_errors','Off');
@ini_set('error_reporting',0);
@ehoanshelt- It’s best practice to make the “field” name all lowercase letters and numbers with no spaces or special characters if possible. What you did will work, but this method is a best practice when working with database fields.
For example:
THIS:
‘Alcohol/Drug Counselor’ => ‘Alcohol/Drug Counselor’
WOULD BE BETTER AS:
‘alcohol-drug-counselor’ => ‘Alcohol/Drug Counselor’I updated Step 4 of our tutorial to reflect this.
@mpodboreski– ALL Piklist applications will work together… so yes user accounts will sync between applications if on the same WordPress install.
@mcdonna– Just added documentation for field parameters, including the position parameter.
Let me know if something on that page needs further documentation.
@mcdonna– Don’t blame yourself for not reading the documentation more carefully… we haven’t documented the fields variables, yet. We’ll get this up and running asap.
Also, please make sure you are running v0.5.3 of Piklist. The Piklist folder structure for themes was fixed in this version.
Let us know if you need any more help, or have questions.
@matthew– The current beta version of Piklist is a development framework, which we will support the creation of applications. You can currently use Piklist to build custom fields for posts, settings pages and widgets.
Once all the kinks are worked out of the beta, we will release applications. You can let us know which applications you want to see first on this forum thread
@mcdonna– The first thing we would like to recommend is to never modify or add to the core plugin files. As soon as you update to the next version, your changes will be deleted. This goes for any WordPress plugin, and WordPress itself.
You can either include your Piklist code in your theme or create a Piklist Plugin. Either way you would need to create the proper folder structure
As for the code, we can’t view the files you posted. Please paste the code on Pastebin and we’ll take a look.
@mcdonna– Thanks for trying out Piklist. We’re currently working on field validation and making it as easy to implement as everything else with Piklist… stay tuned!
@mpodboreski– We really appreciate you taking Piklist through its paces. You’ve definitely helped make it a better product. Thanks!
@k_archie– that’s one of the first we plan on.
