Anthony Burchell

Hi @djosephdesign ! You are correct that this only scans public plugins. Previously the plugin used to run the scans on the server the site lives on which would almost always cause the server to crash due to resources being used. This was not the correct solution especially considering folks were running this on their production environments.

This new more limited build of the plugin was done to give us a better baseline solution that does not put the site in jeopardy. We would love for this to be enhanced in the future for premium plugins, and that should be possible, but at the moment we rely on the Tide endpoints to run the scans. It can only access public plugins and themes.

I can imagine in a future release a way to register custom endpoints to check against if the Tide endpoint says 404, but the current plugin is a first step toward enabling that sort of functionality.

I’ll add a backlog issue to make the error messages clearer in a future release. Thanks!

Glad you were able to get started with Hubs! I actually know a lot about that side of 3D content publishing as I have a company that provides managed Hubs Cloud hosting. https://xpportal.io

I dont have any intention to compete with Hubs Cloud as we actually sell Hubs Cloud hosting, but I do foresee a future where this plugin could have a networking add on for simple webrtc connections between small numbers of people on a page. There would need to be rooms and an entire system built out for that, but in time I’m sure I’ll find the right solution and inspiration. I also want to have versions of this block that allow for presence but no-voip so a space could fit more users at the same time. This is all way out of the scope of what the plugin should solve today but I am looking into ways to make further plugins and features that compliment and extend this one.

Hi there! Thanks for your interest in the plugin. This plugin is supported anywhere Gutenberg content may live. If you are using a page builder, unless it has Gutenberg integrations, you will not be able to take advantage of this block.

If your other post types outside of the builder are using the new editor you should be a-ok to use this plugin. Simply go to the editor and type /three and it should show you the “Three Object Block”

Here’s the page where I have a 3D object rendering: https://3ov.xyz/

And here is a page that has a full environment that you can walk around in VR: https://xp3d.io/pod/

• This reply was modified 2 years, 9 months ago by Anthony Burchell.

Hey there @mgibbs189 ! Thanks so much for the kind words and feedback. I’d like to give you a timeline on where we are on the items you mentioned and why we made some of the decisions we made.

1. The “Model icon” can’t currently be changed after creation

Great feedback, we have a fix in the works now.

On the Single and Multi select fields, we are already hard at work to bring that one to life. If you browse the code you’ll see that we have not yet activated that feature but the code is there and ready. We’re just iterating on the final field solution based on some edge case issues we found so folks don’t get breaking changes in a future update. It’s coming very very soon!

4. From what I can tell, the post types (“Models”) aren’t /?s=searchable and there appear to be relatively few hooks to latch onto currently.

Thank you, both of these are things we intend to explore. On searchability: we have an open issue around making models public and searchable. On hooks: we’ve exposed few hooks on purpose at the moment because our pre-1.0 code is in flux. But we recognize the importance of hooks and want to add them later when we’re sure they will be ready for public use.

5. Considering having boolean fields store a value, even when unselected.

That’s interesting. I think in this case you could use the new single-select field when we activate it soon! On the boolean saving false, are there any particular cases where this is used that you could share? ??

6. Repeater fields! This is the biggest deal-breaker for me, but obviously one of the hardest features to pull off. Is this something that’s planned?

Absolutely understand the need for repeat data. We put our initial efforts in this problem with repeater-like functionality through data relationships. For instance, if you wanted an employee directory where employees can be part of many different model types (maybe departments), you might not want to enter their information each time you added them to some other data model. Maybe you want them associated with some type of “buildings” content model to define what building they work in. In that case, it would leave room for error in data entry and repeat work.

In place of repeaters we made the relationship field so that you can select from another data model (in the example case, “employee” model) to attach their data to that entry in the associated model. Repeater fields are something we’re looking to get feedback on how folks are using them. I would very much appreciate your feedback on how you use them! Being that ACM is completely focused on building content models, we’ve strayed from repeaters because a majority of use cases we’ve found are focused on rendering down to some defined markup that the repeater represents. For headless solutions this makes less sense because it’s up to the application developer to define how those data entries are used. This is not to say that we are against repeaters, we’ve just heard little feedback on how people are using them in non-render based ways.

Would you be open to having a call or chat to talk more about how you would use ACM?

Thanks to the amazing @jeffpaul for pointing out, I missed the link in the post above sharing where you can learn more about contributing to the project. You can find that information and more here: https://www.wptide.org/#contributing

Bonjour @doune, veuillez pardonner les erreurs. J’utilise Google Traduction. Je suis un employé de WP Engine et je tiens à vous informer que nous travaillons à la compatibilité des tests 7.3.

I responded in your previous review but here is a copy of that response just in case you miss it:

Hi Jean, I am an employee at WP Engine. I just wanted to get you a response on this. We are actively working to add support for 7.3 and it will be out soon in an update. I understand that you and many other folks are in need of the feature ASAP and we are doing our best to roll it out as quickly as possible while also making sure that things are tested and secure.

Hi Jean, I am an employee at WP Engine. I just wanted to get you a response on this. We are actively working to add support for 7.3 and it will be out soon in an update. I understand that you and many other folks are in need of the feature ASAP and we are doing our best to roll it out as quickly as possible while also making sure that things are tested and secure.