noahkuhn

Unfortunately that would totally change my workflow, not allowing me to use the Advanced Post Creation tool any more? Is there any more advice on how I could trigger an existing tribe_events post to actually be an event with rows in those extra fields? Again, it works when I manually click “Update” on an event that has had its status changed from draft to publish programatically. At that point I can set it back to draft and “publish” it again via the api and it works correctly. Really hoping there is some trigger I can call to make the post an actual “event”.

Having a similar issue. An event is created by Gravity Forms using their “advance post creation” tool. The event gets created, with the correct dates etc. My workflow is to set it as a draft initially and then at a later date, update the status via an API call to “publish” the event. In my case, I can update the status easily using tribe_update_event. This makes the event appear “published” in the backend, but it won’t appear on the front end, unless I go to the post and manually click “Update”. There must be some step needed to actually update the post and make sure that it is fully available to display on the calendar. I attempted using

tribe()->make( \TEC\Events\Custom_Tables\V1\Repository\Events::class )->update( $event_post_id, [] );

But it doesn’t seem to make a difference. No rows are added to tec_events or tec_occurences. Any help would be greatly appreciated. I see that example is passing a blank array into the second argument, do I need to manually get the date values etc and pass those in?

• This reply was modified 1 year, 3 months ago by noahkuhn.

For what it’s worth, my scenario is that I have a page, with the slug of our-work. This page has some content and a featured image. Then I set up a post type (project) with an archive of our-work. So the page and the post type archive are sharing the same slug… The template that serves them is archive-project.php and I just manually pull in the page’s content via things like get_the_title(XXX) with XXX the page ID.

So somewhere in the latest update, Yoast now doesn’t know that I have an archive for some reason, and the post type archive stuff just doesn’t show up under Search Appearance > Content Types > Project. I tested another post type without a conflicting page slug and it works. Strangely, on the post type archive that shares with the page, it also doesn’t show the PAGE Yoast info, it just shows the default “Project Archive.”

I know this is probably non-standard, and I know I could refactor this and remove the “page” from the site, but then I have to figure out another way to get the page title and content I need housed somewhere else. To my client, it makes way more sense to have it work this way. Perhaps I just make it a page with a custom template and get_posts, but I’m not sure I like that option better. Seems like it should be doable?

• This reply was modified 6 years, 8 months ago by noahkuhn. Reason: added info

Like Rob, this seems to have gone missing with the latest updates… There is no mechanism to edit custom post type archive meta data. Kind of an important piece of this.

https://github.com/Yoast/wordpress-seo/releases

I posted about this too, it’s a huge impact. Very surprised such a marquee plugin has an issue like this.

This seems like pretty basic functionality for this plugin to be useful. If I can only display the events with working links on the “eventbrite-index” template page, and nowhere else (like an area on a homepage), then this plugin is just really bare bones.

After looking through the code, the whole thing seems pretty half baked, especially for an official partnership between Automattic and Eventbrite. Free is free though I guess…

Actually, this can be fixed in youtubevideo.php on line 105. The number “10” is the culprit. That needs to be a string.

Installed this on WP 4.1 and now get the following error at the top of each page in the control panel.

Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /wp-includes/functions.php on line 3495

And thus the default would be

$clear_condition = ( is_front_page() || is_home() );

My problem is fixed by changing line 23 in /smarter-navigation/main.php to be

$clear_condition = is_front_page();

Seems like that should default to clearing on either the homepage or the main blog page no?

Any input on this from anyone?