Posts by sevenspark

Okay guys, let’s sum up and then end this:

1. Don’t spam customers. They don’t like it and it’s illegal.

2. You can only send emails to subscribers who have opted in explicitly to your mailing list – generally this means filling out a sign up form and confirming their email address. There are lots of list management services out there to chose from, including some stand-alone ones over on CodeCanyon. Customer != Subscriber

3. Bedros has already apologized; he’s made a mistake and learned from it. No need to beat a dead horse.

4. AccuData is understandably frustrated; it’s not professional of an author to spam customers and leaves a bad taste in their mouth, so let’s not go attacking them.

@AccuData, since this has been addressed with the author, I’m going to lock this up for now; if you do receive other spam emails from authors, I’d encourage you to write them back and let them know what they’re doing wrong, or direct them to this thread, as they may be unaware. Remember also that authors here are distributed around the world, and not all of them will be aware of American laws like CAN-SPAM. If you do run into trouble, you can always contact Envato support as well, and they may be able to explain things to the author better.

Thanks!

Weird, all your details are blurred out

Yeah, Dashboard Plus isn’t working for me either – could just be a first of the month thing? Or maybe they changed something again that makes it incompatible. If it’s not working tomorrow, I suspect Xaver will look into it

2 year old thread attracting spam. Locking.

quickandeasy said
Hmm, maybe I’m just being narrow-minded.

When I purchase a theme or CC file, I always check the comments to see what issues there are and what the Author has replied with.

Of course, I know that’s a good place to find those answers though.

I suppose my perspective is a bit skewed, too my main product has almost 1,400 comments on it, so you can understand why (1) I’m a bit sick of them and (2) how as the number of comments increases, their usefulness decreases as they become harder to find

That being said, your point about knowing where to look is very important. That’s why I’ve suggested in the past we have standardized links to support and documentation – I think the new Support Tab that was mentioned a few weeks ago is a step in the right direction. In other words, we need standardized access (easy to find) with the ability to customize content (tailored to individual products).

quickandeasy said
I think this would make commenting redundant, which would then result in the author answering the same questions over and over rather than having public info in comments for buyers to read through.

I wish there was some way to actually measure this (percentage of customers who read comments), but in my experience there are a huge number of buyers that don’t read the comments at all, even when they post a comment of their own. Therefore it has been my policy that if there is a question that gets asked repeatedly, it should be published in an easily-accessible location (like the product description or a pre-purchase FAQ page – though a lot of them don’t even read the product description in full), rather than assuming customers will be reading comments – let’s be honest, they’re just not user-friendly to browse.

This is especially true with products with high sales volume, which in turn have huge numbers of comments.

Personally, I would prefer receiving pre-purchase questions solely as emails, so I don’t have any problem if this essentially killed the item comments section. But since different authors have different preferences, it’d be nice to just make these things configurable.

I suspect this varies from marketplace to marketplace as well: item comments probably work pretty well on GraphicRiver; I think they’re severely limiting on CodeCanyon & ThemeForest.

Another advantage to this would be that we could potentially tailor auto-responses to specific products, which would be helpful for authors with a lot of products, or for whom support requests need to be directed to a specific team member.

I think this would be a good idea if we had the following control:

1. Ability (optionally) to show the contact form only on items that the customer has not yet purchased

2. The ability to label this box as we see fit, for example “Pre-Purchase Questions”

The problem is that for those of us that use external support forums, this is just going to confuse customers even more unless we can customize its purpose. Sounds great for pre-purchase questions, but once the user has purchased I would want this box to disappear (and optimally be replaced by my own custom button linking to a support forum)

By the way, the other great thing about this idea is that the email could include a reference to the page it was sent from – I can’t tell you how many requests I get where the customer does not identify which product they’re referring to

Hi 4theme, and welcome.

This is a forum, not a chat room – you don’t usually get a response in under 3 minutes

If you’re looking to become an author, you can find all the information you need here. Best of luck with your template!

I think right now this is a temporary issue where you have users who have purchased and downloaded before the change and are now trying to find the license. It’s confusing because previously they clicked the download button and it immediately downloaded the file, rather than offering a dropdown (I do think that UI could be done better). So it wouldn’t make sense to even click that button again.

However, moving forward, any user purchasing a file will already have clicked the download button, and used the dropdown to download their file. So they’ll know to look in that space for other resources, like the license.

In the interim period, there will be a bit of confusion that we’ll have to walk users through. But moving toward a cleaner interface (all downloadable resources related to an item grouped together in a dropdown) is a move in the right direction, I think.

And like Dzinc said, part of the issue is screenshots of the old layout; those screenshots need to be updated.

Perhaps this would be of use to you

Scout is another useful one – been using it for a while.

By the way, your site is currently up for me.

Before you switch, you should probably run some diagnostics and see why your server was down. Could be you had chewed up all the memory with a leak in some of the code, which you’d want to identify and resolve. Or if you’re on shared hosting you might just have an underpowered account for what you are trying to run. Perhaps it’s simply that the server you’re running can’t handle the current traffic load if the specs are too low.

Anyway, not saying you shouldn’t switch, but there are a variety of reasons a server can go down and it’s not necessarily the host’s fault. That being said, I agree that (mt) is a better choice.

Good luck with it!