Hi Waqar - and sorry to reply again, I know it will re-open your ticket to a must-reply status.
About https://toolset.com/forums/topic/cred-delete-post-acting-weird-on-rfg-views/#post-1988583, we might see slightly different results - however I think we both know what the issue is:
- the trash link trashes indeed the RFG but since RFGs in the backend have nothing to reflect this status we never see any "effect" of it. This is the issue.
- delete link indeed deletes the RFG. This is fine.
As for my last reply, let me clarify that I did not mean you are making a mistake - I know you are doing an excellent job just like anyone else in Toolset.
I observe however this "lets close things" behaviour in other tickets and it really gets me.
I have no issues with "No, we won't fix it."
That is a statement and a decision, and with it, people can make their own decisions.
What I can not live with is stumbling over 3 years old tickets where someone promised "next release will include it, please close this ticket as fixed now" and the client then marks the ticket as "My issue is fixed".
Of course the issue never was fixed and never will be fixed, and when we now re-comment on the ticket we get a statement like "Developers have other priorities".
This within 3 years time to add a CRED Relationships Forms API (just to make an example of the latest such case).
And I want to avoid that this happens - at least to the tickets I open.
Lets be honest to each other and say when things won't get done, and do them when we say we do them.
I've worked with a bunch of other plugins the past year, and I must say, usually it takes a week to fix a bug for them.
It's not that they have no clients or are so little plugins or services, no - big players like WP Grid Builder, BlocsApp, SiteGround or else services.
They care about the problems found and either fix them asap (the fastest was less than 1 hour after report!), or they say "no, sorry, this is not within our plans, please feel free to not use our software, goodbye".
And that is when the reported issue is really more of a "could be/I wish for" report than an actual bug or error or UX issue.
Of course, I do neither want to enter in a discussion about why and how's of companies act differently, nor I do want to tell you how its done, or tell you guys that someone else is better, etc.
I just want to explain to you that it is not the standard to wait for 3 Years to then hear the exact opposed answer as to what was stated in the begin 3 years ago.
It is also not the standard that plugins prioritise new features over fixing broken things.
I can say that because meanwhile I've seen a few such services and plugins in action, both in features and support.
While most of those services are not as wast as Toolset is, at least (and sorry fort this "at least") the service/feature offered works almost perfectly fine, and if not, they get fixed.
This builds trust and avoids frustration. It also builds a name. People will say "This plugin is almost perfect and the Author fixes broken things as soon he can, if there really is a broken thing".
Imagine, in the entire time of using WP Grid Builder (which is basically something like Views) I opened 38 tickets, which is relatively a lot for such an easy to use Plugin.
One of them was a bug. One!
It got fixed in 48 minutes (literally).
The other issues where all wrongly assumed bugs or how-to's and I was doing it wrong or was not looking deep enough (not just by opinion but the author actually showed me how to do it right).
Moreover that guy is practically developing, supporting and marketing his product alone.
Imagine what happens when he starts to employ 50 persons that are like him.
What happens when he starts developing Forms, and other addons.
I am just saying that it is definitely possible to deliver quality services which may be a little more restrictive and do not try to cover the entire world's needs at once, but also don't fall apart in each and every single feature you touch - which is what happens with Toolset are often than not, no matter how small the issues are, many (most) of the Toolset features have some special-snowflake-quirk - yes there are millions of features - but honestly, what is it good for if you need to workaround in each of them to achieve the goal?
Just to make a few examples, like we discussed lately, Forms Fields holding inputs inside a label; HTML Comments not printed; Relationship Forms without an API; Views Maps disappearing if no results are found; Toolset Types Post Type order in menu not really working; Etc, etc etc.
Yes, all small, tiny issues that you can say "do not really stop you to work with the product" and that is true, but it is often something that kind of stops your entire show, and not because of a massive technical limitation but because of silly things, where it just seems that the most complicated, most impossible and hard way was chosen to do things, instead of choosing the simplest, perhaps less :fancy: but more stable option in implementation of features.
Let me not start with Blocks, with its jumping of blocks, block settings losing assignment, corrupted blocks after you left the site for 5 days and come back to edit it, incomplete data availability such as user and term meta, extremely complex and confusing GUI of Views, extreme resource hunger, totally unusable Conditional Block ,and much more.
Note that this is not just a hater-opinion, I actually would love to give Blocks all chances it deserves, and I am not alone with this opinion and experience (I follow social media and see many people with the same experiences of a complete headache when using Blocks). And what triggers me the most with these issues is that you don't need to develop some moon-landing-software to actually see those issues, it is enough to simply create a simple blog to see them - and yet in the videos I see for Blocks training all these quirks are not happening. Blocks are not jumping constantly, no "Please wait - loading" message when waiting for a View of 10 Posts to load in the editor, and so forth. One questions if the plugin used is maybe another software or the videos are not videos of a real world. And again, this is not just me saying it, it's just that most people will not spend 45 minutes in front of a screen to do nothing else but report an issue and perhaps few more to your forum. This might be because it actually costs money (for us) and if one reads the forum he/she'll know that it is likely pointless reporting something that is not literally crashing the world, because it ain't going to be fixed anytime soon anyway- if it ever gets the attention one thinks it deserves. This impression will then lead to the behaviour of "Let me workaround it somehow and wait, maybe they'll fix it one day".
Well, that said, and as others have said, Toolset is a great tool, and the team behind it is composed of great minds. This is not a trial or an attack, it is just the facts we developers and freelancers find ourselves in when working with Toolset and in more than one case it was the reason why clients moved entire websites away from Toolset towards other plugins and more often than not, custom code (which ain't that bad for me of course, it means more work).
Cheers, and please try to not misunderstand me. I'm not trying to correct you or whatever else it might appear. It is plain and simple fact sharing and showing you my point of view.
Thanks...
