By John Wooten on Wednesday, 07 December 2016
Posted in General
Replies 3
Likes 0
Views 183
Votes 0
Hello, Everyone!

Just wanted to jump into what seems like a great Community around a great suite of products (ES, EB, ED, etc.). I have a handful of questions for the Forum Community here and will be as clear and concise as possible with them, posting appropriately and individually (and usually in conjunction with Questions already posted on by other Members).

First and Foremost, definitely want to THANK the StackIdea Team & Developers here - I am not a developer by trade, so I greatly respect your work; the work done on the StackIdea products is simply outstanding. Exceptional Stuff! Additionally, the amount of time given and the access/availability of the Developers here to all of us in the Forum is to be commended: this level of quality application development coupled with high level customer support is at the top of the Joomla Community (and I've used a TON of Joomla applications). I am currently testing out the full suite of products for production purposes on some ecommerce sites I support and my immediate reaction here is: WELL DONE!


  • One initial point to make here that I've noticed about the Support Forums (i'm an avid reader of posts!): I think it needs to be made more clear as to the function of these Forums. "EasyDiscuss" "discussion" "forums" seem to be more used as a "ticketing/help desk" solution by StackIdeas than as an open community forum. I've read the StackIdea creed/mantra on their approach to Support - i certainly get the approach from a business perspective (in essence, to most effectively resolve an issue, backend/ftp credentials and access are modus operandi). However, I'm finding that a lot of questions that I have come upon I cannot find answers to within the Forum because of this approach. Example: I search the Forums for a particular issue I have (just a generic example for reference here: "which fields from ES are mapped/synced to Joomla User Groups?"). Often, a SI Responder has picked up the item as a "ticket", addressed the issue on the Customer's backend/FTP using their private/site admin deets and closed the issue/post as "resolved" and closed it to new replies. That leaves the rest of us, searching the Forums for just this particular question, without any understanding of how the issue was actually resolved. Instead of finding an Answer on our own and applying it (I pride myself on self-sufficiency), we are left to open yet another "ticket" by way of an entirely new post, on the exact same/similar issue. Again, I get/understand the business approach taken here by SI (the shortest distance between two points is a direct line), but I think it creates a "Forum" that isn't really a Forum - it's primary mechanism is instead a "ticketing" system for support. I'd much rather see an open "discussion" as to what happened in the instance so that when I search the Forums for an issue, I can reasonably have a path to fixing the issue on my own based on the "discussion" the entire Forum Community has undertaken. No new "ticket" required


How's that for a long, overly-verbose, first post?! Anyway, thanks to the SI Developers and thanks to the overall Community of Users here - I'm off to make a few more observation posts here on the Forum, and looking forward to utilizing these products and seeing them enhanced even further -

CHEERS!!!
Hello John,

Firstly, welcome on board! I hope you are loving every bit of our extensions and we certainly hope that your journey with us will continue to rock

I certainly agree with your points here and the only reason that we lock after resolving a post is simply because we do not want that thread to get revived after 2 years since the version that you are using is most like much later than what the original post had and to look back at these posts and understand them is going to take a lot of time.

Our goal is to ensure that any bugs / problems / possible bugs are ironed out in every iteration of the upcoming release. If it is a bug, and a problem or a conflict with a template, we will try our best to solve it so that the same problem will not repeat itself. Though, I have to admit that, although we try our best, it will never be perfect and there are times when you have very similar questions but 90% of the time, they are different (they might seem the same though).

One instance would be "EasyBlog composer doesn't load up". There are more than 1000 different factors that causes the composer to not load up and it all depends on which template, modules, plugins that you use / run on the site :|
·
Thursday, 08 December 2016 01:00
·
0 Likes
·
0 Votes
·
0 Comments
·
All good, valid points sir - thx Mark and yes, I am tremendously enjoying EasySocial, EB and ED - my new favorite joomla components!
·
Thursday, 08 December 2016 02:11
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks John
·
Thursday, 08 December 2016 02:16
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post