Sorry Andy. It is a large intranet site.
Basically all of the editors of the site want an image next to their new links that says “new”.
I am doing this now using css. But at some point in time in the future they have to go in and delete the “new” class. This is hard because they forget to do it and forget what date they added things.
My solution (best I can think of is this) to have them add the date in the “title” tag on the link.Example:
<a href="link.html" title="11/20/2012" class="new">LINK</a>
I would then need a js to activate the “new” class if the date is within a X amount of day of the current date – the new class would just display the image after the link when activated.
That is a great idea for sorting but the new links will be jumbled with the old – this isn’t my decision. The people that maintain their pages can do whatever they want. The biggest request I have right now is there is no way for them to mark something new.
Well I have a css class that adds a “new image” but it never expires creating a mess of the pages. These are people who can barely use an editor updating these pages. If I don’t make it simple they will mess it up. Also I cannot use paragraph tags… screws up the editor too much (yes this is what I am dealing with).
Just wanting to get input on something before I get it working.
I am doing all of the templating for a very large CMS … but I have no ability to touch the asp or database. I know it is awesome.
People want to see what links are new on the system that contains about 200 sub pages with their own author.
What do you think is an easy way to show the end user that a link is new (2 months or less) and also easy for the author to fill out?
Example: <a href="http://somegreatlink.com" title="10/03/2012">Some great link!</a> Until Dec 2 it would show... Some great link! (NEW IMAGE) After it shows... Some great link! Am I on the right track here? What do you think? Is there an easier way? Does anyone know of something similar. I feel that others have done this before and I am reinventing the wheel (a poorly designed wheel).
Duotive actually makes very high quality themes that I would gladly pay $50 for. His point is that if a buyer like me pays $40-50 for a crappy theme, and that buyer has a bad experience (because theme is crappy), then duotive will in the long run will have less sales because of the perceived association of all themes on TF.
I am not sure why certain themes sell better and certain good themes don’t. I think for one there needs to be a better description of themes and users should get to see theme documentation. Then we will be less likely to buy a bad theme. I for one give my clients a list of 10-15 suitable themes (from TF and other sites) with a small note next to each one. Then client picks based on how theme looks, certain theme functions, and my notes (and I have to say most of my notes on TF themes has told client that there is a risk that not all functions may work in theme).
All of our comments will be flagged. haha
IE9 is fine. Don’t see why it took so long to make a decent browser. FF has serious memory reallocation issues. Chrome and Safari have plugin issues. Most of your users are using IE… so hope you are coding for them.
Where is the right place to express opinions about themes? I am actually wanting to know. If you say anything about a theme that doesn’t work the comment gets deleted or the thread gets locked. I am not sure that is a good characteristic of a trusted site.
There are very good authors on here that I have a lot of trust for. But their themes don’t always match what client is looking for. I now tend to not trust any author on here unless I have worked with their theme.
It is funny that you bring up comment section. I have witnessed 3 or 4 times over the past month seeing a comment about an author not answering email or major issues with theme, seeing it “flagged”, and then it disappears. This makes me trust the TF process/staff less. I don’t read 100s of comment sections and I have seen this multiple times.
TF is worried about short-term money too much. If you make authors pay for mistakes (by refunding clients quickly when there are major bugs or issues) then you will have much more sales in the long run. If I were running TF I would tell my authors – if you list something as compatible, if you show something, it must work. All native WP features must work. If it doesn’t work your client will get a refund. If we get x number of complaints from client then your theme is flagged. If we get x number of complaints then your theme is pulled. This attitude would lead to good authors making more money and in the long run TF having more trust with buyers. I have spent over $300 the past month on other sites (with probably worse themes but again they work). I am pretty close to giving up on pay themes and just buy the hell out of plugins (never had issues with codecanyon – probably because crappy coders don’t try their hand at plugins).
And let me add – there is nothing worse than buying a theme for $50 and working on a site for 5-6 days and then noticing there are major bugs (admin panel not working in IE9 , feautured images not working, no post truncating, subcategories not working were from my past two buys here).
Yea there is something worse—Envato telling you “work with the author”.
From there I either have to go through crappy code and make the php/jscript/html fixes or basically start over with new theme. I have gone through this roughly half the time I have bought on TF (maybe it is bad luck or maybe I am trying to buy themes too cutting edge) but this only happens 10% on other sites. It really sucks when a client is monitoring and sees their site 60-70% done and you have to tell them that you have to start over.
I do a ton of middleware and dev work—and I also buy a lot of WP themes. I think I can see things from both sides.
@VF – You bring up a good point about support yet you don’t answer it. There needs to be a statement about support levels. Like author has so many days to fix minor bug, so many days for admin issues, customer has right to get refund if basic WP functionality is not working.
I hate when Envato tells me to “work with the author”. If the theme doesn’t work why does a buyer need to work with the author? There needs to be clarity on what is acceptable or not. If someone drew a line in the sand and said if you have these bugs your users can get refund then authors would eventually not release themes with those issues.
It is seriously a joke. I mean a lot of authors can’t even fill out their theme info right.
To sum it up. TF has some very crappy authors. I don’t know the percentages but it is more than 20% and less than 90% haha. These authors are getting their themes approved. More often than not, they are helpful but they do not have the ability to fix things (or they wouldn’t have released it in the condition). TF just lets them keep selling. Even after you get a refund on something because its broke… still for sale. This means that most buyers will scrutinize and associate all of the great authors with the crappy authors – you are all part of TF. As a buyer I have bought 3 themes in the past month at other sites when I wanted something from here more because I am never sure if the themes from here will work—and at $50 I can surely get a working theme somewhere else (might not be as “cool” but it will work).