Nick C
Forum Replies Created
-
Version 1.7.3 is out now with a fix for this issue.
Forum: Plugins
In reply to: [Genesis Custom Blocks] All custom fields are opening in modal when not setVersion 1.7.3 is out now with a fix for this issue.
Forum: Plugins
In reply to: [Genesis Custom Blocks] Open block fields in a modal instead of renderingVersion 1.7.3 is out now with a fix for this issue.
Thank you for your report, @nyamamoto, and sorry for the bug!
We’re working on a fix for this that should be in the next release soon.
Forum: Plugins
In reply to: [Genesis Blocks] All sites using Genesis having display issues as of todayThanks for the report, @raleighwood.
It looks like you were able to resolve the display issue by updating Genesis Blocks (or Genesis Blocks Pro). I’m sorry that this required a manual update on your part, we appreciate you following up in the support ticket.
Forum: Plugins
In reply to: [Genesis Simple Sidebars] PHP 8.2 ErrorVersion 2.2.3 is out now with a fix for this (and for another PHP deprecation notice — see the changelog).
Thanks for your patience while we worked to solve this.
Forum: Plugins
In reply to: [Genesis Simple Sidebars] PHP 8.2 ErrorThanks, @vijustin, that helps! I’ll post again here as soon as there’s an update to fix this.
Forum: Plugins
In reply to: [Genesis Simple Sidebars] PHP 8.2 ErrorThank you for the report, @vijustin, @rameshmahala and @hirejordansmith, and sorry for this error!
We’d like to fix it but I can’t reproduce it with a fresh copy of Simple Sidebars on a new site so far.
If you have time, please could you share the response from this WP-CLI command?
wp option get ss-settings(If you don’t use WP-CLI, you can find the same value in your wp-options table under the
ss-settingskey.)It sounds like the issue might be sidebars with a missing ‘name’, but I’d just like to confirm this before we create an update with a fix.
Forum: Plugins
In reply to: [Atlas Content Modeler] Issue when trying to create a pageACM 0.22.0 is out now with a fix for this.
After updating, your ‘type’ model will be disabled, which will let you create pages again.
You can then follow these steps to migrate the ‘type’ model to a new ID in order to reactivate it.
Alternatively, you can delete the ‘type’ model if you’re not using it, or delete and recreate it manually if you don’t need ACM to migrate posts, taxonomies, or related fields linked to the ‘type’ model for you.
ACM 0.22.0 will also prevent model ID conflicts for future models you create.
Thanks for your patience while we worked on this. If you need further help please let us know.
Forum: Plugins
In reply to: [Atlas Content Modeler] Issue when trying to create a pageThank you for the additional info, @jorgemsilva.
I can now reproduce this by creating a model with an ID of ‘type’ containing at least one field.
I’ll look into this now and update this thread when a fix is available.
Forum: Plugins
In reply to: [Atlas Content Modeler] Issue when trying to create a pageThank you for this report, @jorgemsilva, and I’m sorry for the error.
So far I have not been able to reproduce it. I can create pages with ACM active without seeing the fatal error you mention.
Are you able to share more information about your site setup so I can try again? It would be helpful to have:
1. The site environment info from Tools → Site Health → Info (click “copy site info to clipboard”, then paste here).
2. The content of your ACM models export file (generated from Content Modeler → Tools → Export). You can either paste that here in a code block, or as a link to a https://pastebin.com/ URL or similar.- This reply was modified 3 years, 8 months ago by Nick C.
Forum: Plugins
In reply to: [Atlas Content Modeler] Relationship field – a maximum of five options appearGlad that helped, James! Thanks for letting us know.
There’s an open PR to fix the header issue in WPGraphQL JWT Authentication in case you want to add your voice there to say it’s affecting you:
https://github.com/wp-graphql/wp-graphql-jwt-authentication/pull/118
You could apply the fix from that PR manually if you want to keep using that plugin.
Or for previews you could try the Faust WP plugin:
https://wordpress.org/plugins/faustwp/
The Faust docs are specific to Faust.js (a Next.js-backed framework):
https://faustjs.org/docs/next/guides/post-page-previews
But it should be useable with regular Next.js sites too:
https://developers.wpengine.com/blog/previews-in-headless-wordpress-using-nextjs
There’s also a Discord dedicated to headless WP if you have follow-up questions about previews or authentication with Next.js:
Forum: Plugins
In reply to: [Atlas Content Modeler] Relationship field – a maximum of five options appearHi, James! Thanks for the report. The list should be paginated if you have more than five items.
If you don’t see paginated items, your site might have an active plugin that accidentally strips WordPress’s pagination headers from REST responses. The “WPGraphQL JWT Authentication” plugin is one that has this bug, but there may be others.
Here’s an example that we saw in the past:
https://github.com/wpengine/atlas-content-modeler/issues/443
You could try temporarily disabling other plugins to see if entries in the related items list are then paginated.
Forum: Plugins
In reply to: [Atlas Content Modeler] Relationship fieldThanks for the request, @nazartikhonyuk.
Relationship fields are not yet supported in REST responses. I’m sorry not to have better news for you there. The reason is that relationship data is stored in a custom table (not post meta), so we have some extra work yet to do to support it for REST.
If you’re willing to install WPGraphQL and make GraphQL queries instead of REST requests, ACM relationship field data is supported via GraphQL. This also lets you get data about the related posts in the same response without having to make a separate request.
If you’re only interested in fetching relationship data via REST, I opened a feature request here in case you want to up-vote it or track if it’s added:
https://github.com/wpengine/atlas-content-modeler/discussions/605
Forum: Plugins
In reply to: [Atlas Content Modeler] embed codeThanks for the suggestion, @jaypozo!
The plain text field currently filters HTML output as you noted, but we could add an option to prevent filtering for folks who want to use plain text for HTML embed code.
We’ve added this to our product backlog to take a look at in the future. I don’t have a timeline quite yet, but thank you very much for sharing your use-case here.
As a workaround for now, you could use a plain text field with the HTML link to the TikTok (instead of the full HTML embed code). Then on the frontend you can use TikTok’s oembed API to grab the embed HTML. For example, a request to this URL will give you the embed HTML in the ‘html’ property of the response, as well as other properties that might be useful on the frontend like the thumbnail URL and size:
https://www.tiktok.com/oembed?url=https://www.tiktok.com/@scout2015/video/6718335390845095173TikTok has docs on this here if you’d like to learn more: https://developers.tiktok.com/doc/embed-videos