Dissapeared

Thanks a million Dan Brady!!! –
1. Go to Permalinks
2. Click save

A nice simple solution to what I thought might have been a complicated problem.

worked for me after upgrading to Version 1.0.2 (CPTUI)
with WP v4.1 & ACF Version 4.4.0

Add my name to the list of developers who lost their custom posts with this latest upgrade.

So it sounds like I should just revert to the old plugin and a past version of my site and hope this is fixed for the next update?

This has happened in twice in the past and I set up a staging site to test for problems. While it has been disruptive, I’ve always been able to fix it within an hour. Not this one.

Thank you for any feedback.

Hi wwrogers.

I had Michael to look at my site.

To get it to work. He used/ copied the information from the custom posts.
And somehow got the newest version to accept it.

Contact Michael and i am sure he will find a solution for you.

Nothing is lost, for the record, and you can downgrade if necessary in the meantime, but I’m always willing to help figure out why things go awry.

wwrogers, after you upgraded, did you flush your rewrite rules? What exactly is not showing up any more like expected?

The biggest pain-point has been the converting between settings, and it hasn’t been perfect by any means, certainly not like I hoped.

What is happening is I have 5 lawyer bios posted to a main “Attorneys” page. The posts are appearing on the main page, but when I click on Lawyer A’s bio, then I get a 401 Error Reading. And all the rest.

I’m not sure what you mean by “flush your rewrite rules.” I just updated on my staging site as I said – and I’ll leave my real live site on the old plugin. So I’m safe – just concerned because I use the plugin and like it a lot.

Thanks!

Just visiting your permalinks settings page and hitting save without changing anything will flush them for you. Hoping that’s all that’s required to get your site back up and running, staging or no.

Came here to add my experience:
1. Disappeared everything silently, this is quite serious.
2. Fixed with clicking on Permalink Settings / Save

I’m probably never getting around the permalinks refresh, as much as it pains me. I’m glad it’s all it takes for a decent number of people.

I appreciate that, Michael.

So I had to reset my test site without following your instructions. I had a client issue and we needed it.

So where does this leave me? Should I just not update it on my site and wait until the next update?

I don’t think this route is for me over the long term because of my skill level. But I think I’m going to be using the post plugin for at least another year.

The next update is going to be a very minor one with a couple fixes related to single quotes in labels and a handful of internationalization tweaks, so not anything that’s going to help transition from 0.9.x to 1.0.x. It’s going to honestly be better to get this tackled now and figure out why it’s failing to fully transition in your case.

Was this happening on a non-live, in-development website originally for you? or was it on a customer-facing live one?

It will be a lot easier to figure out things, safely, on a dev site, so I’m hoping for that situation.

Let me know your thoughts on any of this and if you’re willing to possibly let me into an admin area to check on things first hand, if necessary.

I feel like your telling me I have to jump in the ocean and you’re holding my head down and you’re just saying, “just see if you survive.”

I will practice on a development site, but it sounds like I’m going to have to reset the Permalinks, then if it resets successfully, hope for the same on my law firm website? The one that pays me 25 percent of my living and is getting high visibility this month for a blog that was written? It’s not fair really. I wouldn’t have let the development team use your plugin if I had known it was going to be like this. I would have just used a theme with a good shortcode.

I’ll let you know. Thank you.

Sara

Michael, thank you.

The WordPress managed hosting company I use helped me resolve it, with help from your notes on this thread.

Thank you for being a developer who helps the people who uses his plugin. Your plugin does make me a little nervous, but my clients love it.

I honestly hope I’m not giving that impression at all, because it’s certainly not my intent.

There are just hickups/edge cases in this major upgrade that need to be resolved, and I’m being as hands on as possible to help everyone that needs it. All the while I’m taking in the feedback and rolling it back into the plugin with point releases as necessary to smooth the path of people in the future. The biggest issue for people upgrading is the fact that I changed parts of how the settings were saved, which was intended to make it a lot safer to update settings quickly or many at the same time(reported issues in the past).

Putting concerns of the new UI to the side for the moment, things ARE still good overall on this side of the new update.

Yes, there have been a decent handful of cases where the permalink refresh is all that was needed, and everything fell back into place afterwards, but it hasn’t always been the case each time.

Regarding the last reply from you Sara, is there any way I could get feedback from the people who helped about what was going on for you and what fixed the issues? You’re welcome regarding any and all help. Future updates should be a lot smoother as I won’t have need to convert existing saved settings.

I’ll send feedback through your website.

This weekend. I’m happy to help.

Hoping to have more rewrite issues ironed out after someone pointed me to the following fact

var_dump ( ! empty( '0' ) ); //evaluates false

So I redid some parts that may have string zeros saved from the old settings, and properly pass the correct value based on that. It’ll be fixed in 1.0.3.

Otherwise, I await the feedback ??