rpetersnmt

Elliot fixed us up! 4.4.7 is out and solves this…thanks a million. ??

Found this thread as well:
GitHub – Relationship field not selectable on WP 4.5

If anyone has an update (via another support channel) could you please report back here? Or perhaps you could post a link to any other/related threads? Thanks in advance!

Ditto…I posted to ACF Support as well:

WP 4.5 – ACF Relationship ERROR ?

This is creating all sorts of challenges for me with multiple sites…hoping for a fix soon. ??

Okay…I updated, re-associated and she’s fixed up. Thx!

Hi Michael…I saw that you pushed out 1.0.4…thanks for continuing to work on clearing out these lingering bugs.

I tried to update from 0.9.5 to 1.0.4 and after doing so (on a dev copy) I was still left with a loss of associated taxonomies. My CPTUI-created CPTs are no longer “connected” to their custom taxonomies and this ends up breaking a number of things on my soon-to-launch site.

Any more thoughts? I understand what I need to do to fix it (just re-associate the taxonomies) but I’m stalling to see if you’d like me to help you troubleshoot. I feel like I have a situation here that could be helpful (problem site and easy to clone “dev” for troubleshooting). As soon as I apply the fix to my production site this opportunity will go away.

Anyway…I’ll stall a couple more days before fixing…..but please do let me know if I can help. ??

Ross

Thanks for the message/support here. I’m afraid going straight from 0.9.5 to 1.0.3 still resulted in breakage. Because I host with WPEngine, I’ve left the “Development” site at 0.9.5 and just made copies on my “Staging” to test. I can make you a user there too if you’d happen to like to test.

I’m not in a HUGE rush to get this updated since everything is working fine on 0.9.5, so if you’d like to use this as an opportunity to troubleshoot, please let me know. ??

Otherwise, I’ll wait until 1.0.4 and try it again, fresh from 0.9.5.

Thx!

Hi Michael….I’m afraid I’m in the same boat here on a project where one of my CPT’s fails after updating to your latest version of CPT UI. This has been the case for the last few versions and I keep rolling back and procrastinating reaching out to you.

In any case, I sat down tonight and tried to update to your latest version 1.0.3….and still no luck. SO…I chased it down a bit myself and revealed that my issue seems to be the fact that custom taxonomies that I’ve assigned to custom post types are being lost.

I’ve read through a number of other support threads here and tried things like visiting the “Permalinks” page to flush the rewrite rules…and I even loaded/saved each of the custom post types and taxonomies in my site…no luck.

However…if I manually re-attach my taxonomies to the CPTs, then things come back to life. Certainly I’ll go that route if I need to, but thought I might be able to help you troubleshoot this issue in the meantime.

I have a working DEV version of my project with CTP UI at 0.9.5….would you like me to add you as a user? Perhaps you can look at how I have things configured and see why those cpt/taxonomy connections are being dropped upon upgrade.

Please advise..thx! rp

I decided to look into this a bit more…

The good news is that this double slash probably doesn’t affect the image getting rendered. See here:

https://unix.stackexchange.com/questions/1910/how-linux-handles-multiple-path-separators-home-username-file

The other bit is that I added a one-liner to the plugin to get rid of the double slash, at least in the case where it was affecting me:

Add the following so that it becomes line 305 of wpthumb.php:

if ($subdir == '/') { $subdir = ''; } // hotfix for double slash issue

Obviously this isn’t a permanent fix and it will get overwritten on the next plugin release. If a plugin author is following a long, maybe you could consider a bit of a check here for situations that would generate a double slash situation.

Or…maybe its all moot, since it seems to work fine for me with the double slashes.

Great plugin! Thx!

I’m giving WPThumb a shot for my on-demand image needs and found this same double slash issue. It doesn’t appear to be creating an issue with the image rendering, but I too am wondering why it is there? Anyone? Thx!

Hi Jeremy…thanks for the note.

Ya know, I’m embarrassed to say that (after lots and lots of email with my client), I think there was a misunderstanding and they were not correctly checking the correct boxes within Publicize.

What happened is this:

– I added a filter to prevent my custom post types from auto publishing to the social networks.

– I also added a required checkbox (for the client) where they had to check the box indicating that they’d verified whether or not they wanted to post to social…and where I gave clear instruction on how to properly check (or not) the publicize checkboxes for the various networks that were/are assigned.

– Every time a post was made, I’d see erratic results…sometimes posting, sometimes not…just a mess. I’d then call and review the steps with the client and they assured me that all was being done correctly.

– Finally, I decided that the client couldn’t be trusted…I stripped my filter out so that Publicize was again working like it does “stock” and the checkboxes being auto-selected. I then revised my “required” metabox to say that the would need to de-select any network that shouldn’t be posted to automatically. I called the client and explained the change.

– Since then….all has been working perfect.

So…either there’s a bug with the filter that deselects publicize networks (initially) or there was some serious human error going on. I strongly suspect that it was the latter.

Either way…I think that Publicize and my custom post types are all getting along just fine now.

Thanks for the follow up. ?? rp

Same exact thing happening to me here too….

Or…perhaps there’s a way (filter/hook) to force LLA to use a “translation” file? I’m envisioning that a custom translation could be created to swap out the (currently English) text with different English Text statements….if one were so inclined. Could something like that be done?

Try adding this to your functions.php:

// Filter Yoast Meta Priority
add_filter( ‘wpseo_metabox_prio’, function() { return ‘low’;});

Try adding this to your functions.php:

// Filter Yoast Meta Priority
add_filter( ‘wpseo_metabox_prio’, function() { return ‘low’;});