• Resolved katrinaglover

    (@katrinaglover)


    Hi there,

    I currently use Magic Fields 2 for custom fields and I’m trying to extend some portfolio items from my “parent site” to a sub site. Unfortunately, I cannot get any of my custom fields to show up. I’ve added the custom post type and group name into the white list area with no luck.

    INSTALLATION: WordPress 4.5.3; plugin is activated across entire network; custom fields only exist on “parent site”, custom post type exists on both parent and sub sites.

    NOTE: I did test with ACF and it worked fine but I’m hoping that it will be a simple fix as I would have to recode and redo the entire portfolio if I have to switch over.

    Please let me know if you have run into this before and have any suggestions.
    Thank you!

    https://www.ads-software.com/plugins/threewp-broadcast/

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author edward_plainview

    (@edward_plainview)

    Where can I find this Magic Fields 2 plugin? It doesn’t seem to exist in the plugin repo.

    Thread Starter katrinaglover

    (@katrinaglover)

    Thanks for the quick response! I just checked and it looks like it’s been removed. Not sure why; it’s been in there for years. You can also download it from here: https://magicfields.org/

    I checked and it’s the latest version.

    Appreciate the help!

    Plugin Author edward_plainview

    (@edward_plainview)

    The latest version of MF2 does not exist in the WP repo and the latest update was 6 months ago.

    I’m trying to decide whether there is enough demand for a 3rd party plugin add-on for MF2. Do you know how many users that plugin has?

    How long would it take you to convert the MF2 fields to ACF fields?

    Thread Starter katrinaglover

    (@katrinaglover)

    I’m so sorry; for some reason I am not receiving any emails of follow up ??

    I do not understand why it’s out of WordPress repo (I’ve actually emailed the collaborators to see what’s going on).

    I don’t remember how many times it had been installed but I usually don’t trust a plugin that hasn’t had favorable reviews and isn’t widely used. I wish I could help more in that department.

    I do know that there has been at least one other question regarding Magic Fields 2 in this plugin’s support forum (I believe they had the same issue).

    For myself, I use Magic Fields 2 on every website I build so to switch from Magic Fields to ACF entirely is not an option for me. I will be honest and say that this is the first site that has required the ability to cross publish content and I estimate the time it would take to convert from MF2 to ACF to be around 48hrs (I’d have to rebuild an entire portfolio).

    Thank you, again, for your quick response and I apologize for not seeing it earlier. I’ll keep this window open and refresh periodically as the email notification isn’t working for me.

    Plugin Author edward_plainview

    (@edward_plainview)

    Perhaps a conversion script would be an idea? How does the MF store its data, compared to ACF, do you know?

    Anyways, get back to me on the repo thing – if they put it back in the repo, or at the very least, release some user numbers, then I can write an add-on to add support for MF. If there are enough users, then I could be convinced.

    Currently, I would very much suggest using ACF, seeing as it has … what? A million users? And Broadcast support for all types of weird ACF fields is very, very mature.

    Thread Starter katrinaglover

    (@katrinaglover)

    Unfortunately, I do not know. I do know that when I played around with the ACF interface, it wasn’t quite as user friendly as MF2 (it could also just be because I’ve used it so much that I find MF2 much easier to set up/navigate).

    I’ve queried the contributors to see their response on users. As I have over 5 years and countless custom projects built, code written, etc. I’m very hesitant to switch.

    Thread Starter katrinaglover

    (@katrinaglover)

    Hello,

    I received a response from MF2. The plugin has been active on WP for 7 years and has(had) over 140,000 downloads.

    Not sure if this meets your quota but thought I’d let you know.

    Thank you so much for your help!

    Plugin Author edward_plainview

    (@edward_plainview)

    I’ll have me a look and see what I can do.

    Plugin Author edward_plainview

    (@edward_plainview)

    Yeah, this is going to require a new add-on. MF2 has tables all over the place, so copying over the field data – especially fields that require special handling like image fields – is going to be complicated.

    The add-on will work kinda like the ACF add-on: it detects which fields are used in the post, what types of fields, copy images if necessary, and then assign the correct field IDs on each child blog.

    Which kind of fields are you using, btw?

    Plugin Author edward_plainview

    (@edward_plainview)

    Development is going badly. Why? Magic Fields 2 is badly coded.

    How I figured that out? I have WordPress debug mode enabled, which displays all sorts of warnings when authors are not coding properly.

    I exported the fields from one blog and tried to import them to another. Didn’t work. The export function outputs PHP warnings which breaks the export file. So I exported again but this time switching off all debug info.

    I imported the file and was rewarded with the imported fields… and a ton of WordPress warnings tell me how mf_register_post_types is not registering the post types properly.

    Try it for yourself. Set WP_DEBUG to true, and then try to export and import fields between blogs.

    This is NOT good karma for the MF2 developers. Why did they say that they aren’t on the repo anymore?

    I’m not very tempted to continue working on this, to be quiet honest. It’s one thing to write a compatibility add-on for a plugin, it’s another to write one for a badly coded plugin.

    Thread Starter katrinaglover

    (@katrinaglover)

    Thank you so much for looking into it and starting to work on it. I understand completely if it’s not an easy thing. Please don’t worry about it! For now, I will duplicate the content (with some changes) and look into making the transfer over to ACF.

    The reason they gave for leaving WP was a “disagreement”. There was no information given beyond that.

    Thank you again for your help and quick responses. Very appreciated!

    Plugin Author edward_plainview

    (@edward_plainview)

    > disagreement

    Sounds sketchy to me.

    > look into making the transfer over to ACF.

    A nicely written conversion script from MF2 to ACF can be reused and therefore save you time. I wonder if there is one available anywhere.

    At any rate, Broadcast has great support for all types of weird ACF fields and combinations (repeaters in repeaters), so your switch to ACF is a great idea.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Magic Fields 2 Custom Fields Support?’ is closed to new replies.