Package - Inline PICK form
Im using v1.0 on WP 3.0 Pods CMS 1.8.8
Thanks for the submission clarinetlord, however in my installation the new inline values are not assigned to the pod item during creation. The values are added to the respective pod, but appear in the multi-select pick area unchecked. I have to go back to the pod item that I just created and check the box in order to assign the newly created value.
I can do a video screen capture if you would like to see first hand.
11 Answers
Thanks for confirming this. I believe I have fixed the bug and I've updated the package again.
Thanks for letting me know. I have fixed this bug and updated the package. Let me know if everything works for you with the updated version.
v1.01
No problem, however I am getting an SQL error, but I'm not sure if it is related to the way I updated.
Error: SQL failed; SQL: SELECT id FROM wp_pod WHERE datatype = 21 AND tbl_row_id = LIMIT 1; Response: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'LIMIT 1' at line 1
To update I dropped the two helpers and ran the import with the 1.01 code. Is this the way to update? It would be great to be able to just run the update over the top in the package import which would make the necessary changes to the existing code. I did try this first.
Thanks
edited Jun 26 '10 at 4:44
I'm not sure why you would get a SQL error; When specifically do you get the error? You might want to try the whole process again and also detach the helpers from the pod and column first before dropping them.
See demonstration via video screencast - 12.7 MB
The error appears after saving the pod item. It saves the 'category' and attaches it to the item (although still having issues with the checkbox remaining unchecked).
Here is the error copied from that screencast:
Error: SQL failed; SQL: SELECT id FROM wp_pod WHERE datatype = 21 AND tbl_row_id = LIMIT 1; Response: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'LIMIT 1' at line 1
Thanks for making this. Two things I noticed that might be affecting the helpers. One is that you are using a maintenance mode plug-in of some sort, so try turning that off. Two is that I noticed your PICK column is bi-directional. I haven't tested this package with bi-directional PICK columns, so I would try removing that for now and see if that works (I don't think you need a bi-directional in your case anyway).
No problem. I have tried turning off the plugin WP-Maintenance Mode, and also removing the bi-directional link. I am getting this error:
Error: Cannot add relationships; SQL: INSERT INTO wp_pod_rel (pod_id, sister_pod_id, field_id, tbl_row_id, weight) VALUES (128, 0, 102, , 0); Response: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' 0)' at line 1
The new item is added to the pod, and the inline item is also added to it's respective pod, but the checkbox is not enabled. Navigating back and checking the box produces no errors after saving.
I think I've found what the problem is, but I want to make sure before I update the package again. If you add some keywords manually, then add an image pod with new inline keywords, does that work? I think the helper may be breaking if there are no related pod items begin with.
This is a summary of the tests I just completed:
PASS - Add 2 new keywords via the Add Keyword Edit page. Add new image, check the boxes next to these keywords. Save. Navigate back to list, edit the image and add a new one inline. Save. All three keywords are applied with no error.
FAIL (Same SQL Error) In the Edit page of the same image, uncheck the box of the three keywords, add new one Inline. Save. Error.
It seems the result is consistent with your findings.
Great, it's working fine now. I also recreated the bi-directional link as I will be calling images from a keyword page at a later stage, and to also test the functionality with your helpers. Although not a comprehensive test, it does also work fine.
Thanks for the speedy turn around with the update.
Awesome. Thanks for your help in testing this.


