Joelle

Hello! I do have show in nav menus checked for all applicable items. (Which is all of them). Still nothing shows up on the menus area. There is no caching involved either. Very strange!

I forgot to tell you it would be re a site for Talia so if you see that stuff, that’s my client. ??

Hi Michael! ?? Thanks for responding so quickly.

I resolved the Collections issue, it was the first thing you said. I checked for it like 10x, of course, but I guess I just didn’t *see it*. You know what I mean. lol

But the other part… all of them are set to show in the menu so I’m not sure what’s up. I’ll send you the info, thank you!

It has to do with Yoast/Gutenberg not renaming the slug and then assigning a redirect. It’s very odd, but hopefully it’ll get sorted. ??

https://github.com/Yoast/wordpress-seo/issues/9189
https://github.com/WordPress/gutenberg/issues/7129

“Has archive” is set. There is no page called “books”. Everything was totally fine until this last update. Very odd! It may be another plugin so I’m doing that dance right now. I’ll report back! ??

No, I totally agree. I wasn’t suggesting you do it now. but if you ever do add a settings page, you might consider it. ??

Yup! I mean, it probably won’t apply to most people, but I guess to some it might. ?? If it were an option to be ticked (posts, pages, cpt) then people could allow that function on those specific things instead of only on single posts. They could do all or just one or two.

But that’s literally like a “if you have nothing else to do or even want to” kind of thing.

I made a discovery today! I have a client who has her books (including ‘future posts’) set up as pages. It took me about 20 minutes to realize the reason those were still showing 404 is because they aren’t using single.php. DUH, right? (You’d think I haven’t been doing this for… *coughcough* years.)

It was an easy adjustment in my functions file, but if you ever decide to include a settings page and want to include that option it was just:

if(is_single() || is_page() && $wp_query->post_count == 0)

Not that you need to – that’s a fairly unorthodox usage. ?? But I figured I’d share anyway.

YASSSS! It activated without a hitch. ?? Perfecto!

I put in a ticket with my host to move it to a server with 7. I’ll report back when it’s done. ??

Both clients are using WP 4.9.8.
the one where I get the error is using PHP version: 5.6.30
the one where it works (glynn) is PHP version: 7.0.30

Alas…

Plugin could not be activated because it triggered a fatal error.

Parse error: syntax error, unexpected '[' in /home/cassiecl/public_html/wp-content/plugins/the-future-posts/includes/main.php on line 404

Alas…

Plugin could not be activated because it triggered a fatal error.

Parse error: syntax error, unexpected '[' in /home/cassiecl/public_html/wp-content/plugins/the-future-posts/includes/main.php on line 404

Hello! Sorry so quiet, been super busy. ??

I was able to get the permalinks to load without the additional snippet or any additional plugin, so we’re good to go there.

Thank you so much for all the improvements.

Hello hello! Sorry for my silence, I’ve been swamped. ??

I’m still getting an error even with 1.3.5…

Parse error: syntax error, unexpected '[' in /home/cassiecl/public_html/wp-content/plugins/the-future-posts/includes/main.php on line 390