@pixelentity Thanks for posting this. I don’t surf the forums a lot any more, but I feel like it’s rare to start reading a thread like this and see that it ends positively with resolution. As an author making the change to full GPL, this kind of advice (along with Chris’s advice, as well) does help to make me feel little more comfortable about such a big transition.
lol never mind… Of course there is already a heated thread started about this days before. http://themeforest.net/forums/thread/100-gpl-author-exclusivity/92299
Keep in mind this is just a general discussion forum. I think they mean for you to you post your question here in the discussion for that product:http://themeforest.net/item/core-minimalist-photography-portfolio/discussion/240185
There is actually a common cause for that I’ve seen several buyers run into. —There is this classic mistake people do when installing it a theme from ThemeForest where they install the entire ZIP package they downloaded as the theme. Usually this happens, but on some servers, it will actually allow the theme to install and seemingly work.
So, a common side effect of this is the issue under Appearance > Menus that you’re describing; it happens because style.css is not in the root directory of the theme. Is it possible when you installed the theme you did not upload the correct folder of files? Your style.css file should be located like this on your server where you have WordPress installed:
Also, sometimes people upload the their correct theme.zip file and unzip it with cPanel or some other online file manager and inadvertently end up with:
This would also cause a similar issue in many cases.
Imagine if you release a item, a troll seller that didn’t like your item because it can sell too much can just report – your item will be hidden for one day and you’ll loose too many sales. Far of be fair, right?
I think the users that stolen themes are banned by the staff as I remember.Regards, Rafael
They are not banned, A author stole my theme, uploaded it for sale, he was found guilty and the theme was taken down.He is still an author today and doing ok
I had a similar experience, except for Envato did delete the author’s account. So, while sure he could sign up again, he did have to give up his account where he was somewhat established and had about 5-6 items selling in his portfolio.
Yup, I too came here looking for an answer because when I click the “make all as read” button I’m also getting a 404 error, and my comments are staying put.
I just got a pretty simple, straight forward response from Envato support on the ticket I opened this weekend on this topic essentially just saying no to inclusion of FontAwesome, which is about as open-source, clearly licensed, and well-known as an icon-font could be. So, I’d imagine that doesn’t look positive towards the topic as a whole.