[Resolved] Report Beta bug?

[Author]

Posts

[Gavin]

Hello

I am running Toolset Types: Version 2.3-b2 and Views Version 2.6-b1 as I am using the Many to Many relationships.

All was working fine yesterday and I have made no changes to the website. Today, I upgraded the other Toolset components (e.g. Views) to the most recent Beta version and I am getting this error message on Single Post pages:

Fatal error: Uncaught exception 'RuntimeException' with message 'The query limit has not been set. This is necessary to ensure the scalability.' in /home/bzzkttco/public_html/wp-content/plugins/types-access/vendor/toolset/toolset-common/inc/m2m/association/query/association_query_v2.php:225 Stack trace: #0 /home/bzzkttco/public_html/wp-content/plugins/types-access/vendor/toolset/toolset-common/inc/m2m/association/query/association_query_v2.php(255): Toolset_Association_Query_V2->build_sql_query() #1 /home/bzzkttco/public_html/wp-content/plugins/types-access/vendor/toolset/toolset-common/inc/m2m/association/query/association_query.php(173): Toolset_Association_Query_V2->get_results() #2 /home/bzzkttco/public_html/wp-content/plugins/wp-views/embedded/inc/filters/wpv-filter-post-relationship-embedded.php(514): Toolset_Association_Query->get_results() #3 /home/bzzkttco/public_html/wp-content/plugins/wp-views/embedded/inc/filters/wpv-filter-post-relationship-embedded.php(440): WPV_Post_Relationship_Frontend_Filter::get_setting in /home/bzzkttco/public_html/wp-content/plugins/types-access/vendor/toolset/toolset-common/inc/m2m/association/query/association_query_v2.php on line 225

[Gavin]

Ok... I needed to delete and re-create the filter.

[Gavin]

Okay... If I switch the filter to select the many-to-many relationship it breaks with the error message above. If I select 'ANY' then it works. This bug still persists.

[Gavin]

Also... just noticed the Custom Fields and Relationships menu tab is not working - I get a spinning bar.

[Gavin]

Screenshots of two hanging screens in the admin panel.

[Beda]

I am a little surprised that you where able to "Today, I upgraded the other Toolset components (e.g. Views) to the most recent Beta version" from the Views Version 2.6-b1, because, that is the only version ever released of this beta.

Types is in beta-2 and Views in beta-1, and according this, those versions should already have been active on your install - making it impossible to upgrade.

Eventually you updated another Toolset Software?
The Beta's should not be used with stable software yet.
They should preferably also not be used on any existing install, and never on production sites.

In the best case, the Beta's would be used on a fresh local or online development site only.
https://toolset.com/account/downloads/ > beta

Beta versions are special development snapshots, which passed partial tests. Usually, you should use beta versions to test upcoming features or when supporters recommend a beta version to fix a known issue.

Now, I downloaded the beta's and set up an install.
As expected I needed to do this on a fresh install, to get all new features working.

I set up 2 post types, and created a relationship between them.
I set up a View and tried to replicate what you see, but you cannot set up a relationship filter between any and none.
You can only setup a relationship filter between any and:
- Post where this View is shown
- The current post in the loop
- Specific:
- Post with ID set by the shortcode attribute
- Post with ID set by the URL parameter

How did you setup the "none" argument?
I suspect you did not finish to complete the "Select Post Type" in the Filter option "Specific".

In any case, the error was not appearing.

I suggest if you still encounter this error, to send me a Site's Snapshot, so we avoid ping pong discussions and I can try to spot the cause of it faster.

[Gavin]

Thanks Beda. I am aware of the limitations with Beta version(s) but though it might be useful to provide feedback.

I have a very simple Many-to-Many relationship set up between two post types - Sounds and Patterns.

The view to show the many-to-many relationship is inserted on a layout for a single post type - e.g. Sounds.

1) If I select the many-to-many relationship in the view then the page does not load and I get the error as mentioned above. See screenshot1.

2) If I select 'any' in the view the I also get the same error message and the page does not load. See screenshot2.

3) If I select 'any' int he view and a specific post type I get the 'none' coming up - see screenshot3 - BUT... the page loads correctly.

I am unable to view the Relationships or Custom Fields panels in the Admin panel. They are hanging.

I am happy to uninstall and reinstall but clearly since upgrading a component something has caused it to go wrong.

[Gavin]

I am also unable to 'disconnect' the many-to-many relationships when editing the post types.

[Gavin]

My guess is that somehow the database has become corrupted. I will re-install.

[Beda]

This most likely looks like the Post Data cannot be pulled, hence probably either is not existent or is corrupt, yes.

I see you use Layouts? This beta plugins should not be mixed with stable versions.

I also noticed that if you install the Betas on an install where at any time previously a stable version was active, half of the new features is not working as expected - and that is expected.

I suggest to make above test again on a fresh install, where for me it worked fine.
If then the issue is still replicable, I suggest you go ahead and send me a Site's Snapshot.
This will help me to solve the issue and feedback to the Developers.

Thank you!

[Gavin]

Thanks Beda.

I hadn't previously installed stable versions of Types and Views but yes, I am using all the other Types plugins too. Although the site isn't a production site, I have reverted to the most recent stable versions and will re-implement the many-to-many relationships the 'old fashioned' way - with an intermediary parent post type.

Thanks again. Hope you have a great weekend.