Oh, it was actually three days ago, when my client bought the styles, not last night. (my mind playing tricks on me) He started a ticket the same evening asking for a refund for one of the styles he bought, which hasn't yet been answered. He hadn't started a ticket for this issue yet.
Hey Mike. I have a client, who just bought a style from you (actually two), but he'd like one refunded if possible.
That isn't the biggest problem. He is trying to log in to get the UI.X add-on so I can install the style, but he can't log in. He also can't reset his password...
Out of pure curiosity, I'd like to know why you chose LESS over SASS.
Edit: flew over some more replies (yes, I wrote this before reading all the replies) and noticed some answers to my question above.
As for a PHP compiler for SASS, there is also one. http://leafo.net/scssphp/
Hehehe....I am surprised Shawn said this. He answered his own wondering why ES is faster than Sphinx in his comment about its memory requirements over Sphinx. Using more RAM is the simple answer to the price you always have to pay for better application performance.;)
What is missing is a voting system here, so suggestions can bubble up. Theoretically likes can do the same, but I'd want something more prevalent to show more interest means a suggestion can climb up the "to-do list". That alone generates more interest and also more activity for suggestions.
Well, closing a suggestion at all is basically a customer support no-go. If there is a lack of interest, then that simply means the suggestion didn't get the attention needed to get it done. There is no need to determine it as closed or "off the board".