jcollier
Member
I have a back-end admin menus conflict between Gravity Forms and WP Types & Views.
- With GF and Types activated, both appear
- With Types and Views activated, both appear
- With GF, Types, and Views activated, only GF and Types appear (Views disappears)
In other words, activating GF causes Views to disappear.
No other plugins active on this site.
Any suggestions as to how to diagnose this problem?
jcollier
Member
Even with the most recent update to 1.6.3.3.4, I'm still having the same problem:
When I activate Gravity Forms, another plugin, WP-Views, is removed from the back-end left-column menu.
I asked you and them about what might be causing the problem. They are perplexed. I haven't heard back from you.
Do you have any suggestions as to how this problem might be diagnosed?
This problem prevents me from using Gravity Forms plus custom types to create new posts.
GZA
Member
We ruled out using Types & Views for our project as it's a beta product, or it was last time we looked.
At the end of the day, it's probably better to create types and views by hand than relying on what is probably a buggy product judging from the iffy UI.
jcollier
Member
I'm surprised to hear a developer dis another developer, especially since I seem to remember being told to hand-code my forms when Gravity Forms was in its early days, too ;)
In any case, WP Types & Views is now post-beta and in active development by the WPML team, and it's been working flawlessly. I haven't made that particular site in my network public, but the rest is already active: http://mainelearning.net/
However, the problem is specific to one site in the network. So, I've created a new site, exported all of the Forms, Types, Views meta data, and will load it up!
@GZA - let's keep it friendly please.
GZA
Member
I actually wasn't dissing anyone. Last time I looked Types and Views was flaky and was in beta and I didn't care for the UI as it goes against best practice. I have no problem expressing such opinion especially as it wasn't a free product - it has a price tag!
Just calling it how it is. That's me. Nothing personal.
Okay. Thanks
jcollier
Member
Hey, following even more research, it turns out there was no reason to point toward a WP-Types problem anyway. For whatever reason, it was a plugin called PS-Taxonomy-Expander that conflicted with both GF and Types.
So, now both plugins are robust and dependable again.
Right on, thanks for letting us know.
