Forum Replies Created
-
AuthorPosts
-
agorski
ParticipantHello Long,
I see the fix for this did not make version 1.2.14. Is there anything I can do to help move this along?
September 8, 2016 at 5:40 AM in reply to: Groups should be native functionality, not a premium extension #4038agorski
ParticipantThanks for the recommendation. I'm currently using TGM for some theme stuff, but not for my plugin. I guess I'm more concerned with the idea of... let's say I create a plugin that uses Metabox+Groups for custom field management. I could TGM-require Metabox Core and Groups. I could TGM-require Groups and bundle the Metabox Core with Composer. Or I could TGM-require nothing, bundle Metabox Core with Composer, and manually include the Group extension inside the plugin files somewhere using require_once or something. All of those are acceptable uses?
September 6, 2016 at 10:50 AM in reply to: Groups should be native functionality, not a premium extension #4023agorski
ParticipantCool, that makes sense. How should I handle the situation of natively including Metabox Extensions in a plugin or theme? Groups would be a required extension for anyone using the plugin? Or is there a way I can bundle it within the extension without listing it as an actual plugin on the site and still be OK?
September 3, 2016 at 4:38 AM in reply to: Groups should be native functionality, not a premium extension #4006agorski
ParticipantAlso- it would be great if there were support for using the extensions with Composer somehow. I'm not sure how you'd manage access, but it might be a neat idea.
agorski
ParticipantYeah, it's a button inside of a metabox that triggers it. I was able to kind of hack in the functionality by just triggering a click on the "Clone" button, locating the :last clone, and iterating through its fields. This is actually good enough for now, I wouldn't consider this a feature request, I was just curious if there was a built-in way.
agorski
ParticipantI'm also experiencing this issue.
It'd be nice to have somewhere to set or disable the defaults for all field types.
November 19, 2015 at 4:49 AM in reply to: Text Fields dont save (MB Group 1.0.2) (Meta Box 4.7) #1760agorski
ParticipantI'm also experiencing this issue.
September 11, 2015 at 3:54 AM in reply to: WSYIWYG seems to be broken when using groups - sorry to reopen #1417agorski
ParticipantJust FYI, even one javascript error in the console can cause all of the other javascript on the page to break.
agorski
ParticipantActually, after testing this a bit more, here's steps to reproduce:
Create a few items. They can be of any "content type".
Save the page.
Create a new item (New Item A).
Save the page.
Re-order the item anywhere. Notice where you leave it. I suggest re-ordering the new item into the #2 slot, just so it's easy to remember.
Save the page.
The new item is in the correct slot, right? Awesome.
Create a new item (New Item B), and leave it at the end of the list.
Save the page.
New Item B has now replaced New Item A in slot #2, and New Item A has disappeared.Also, after this point, continuing to add a new item will continually replace the item in slot #2- New Item B will be replaced by New Item C, and so forth. If you add multiple items at once, the first New Item X will replace whatever is in slot #2, and New Item Y will fall at the end of the list.
agorski
ParticipantHey,
Thanks for the quick response! You were right, it was related to using select_advanced, switching to a regular select resolved the issue I was having.
Should I update all plugins in the bundle, or were the only changes within the conditional logic plugin?
Thanks again!
agorski
ParticipantI'm still having trouble getting this to work after the update. Is there special syntax for using it within a group?
I'm trying to have fields hide/display based on a select_advanced value within the same group, and it seems like no matter what's selected in the select_advanced, the hidden or visible statement always evaluates to true.
agorski
ParticipantIt says that this has been fixed in v1.0.2 on August 5th in the update notes for Conditional Logic - https://metabox.io/plugins/meta-box-conditional-logic/
However, downloading the core extensions bundle from Gumroad, I still get v1.0.1, and downloading from my metabox.io account I get v1.0.
-
AuthorPosts