Posts by OriginalEXE

1484 posts
  • Has referred 1+ members
  • Has sold $10,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Made it to the Authors' Hall of Fame
+3 more
OriginalEXE says

:D Thanks for sharing, really, I did not notice it. Do you know if there is a way I could receive an email on each WordPress version release? Could be really helpful…. EDIT: just noticed that WordPress 3.7 is not yet in the software list :)
Check the form on the right: http://wordpress.org/download/
1484 posts
  • Has referred 1+ members
  • Has sold $10,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Made it to the Authors' Hall of Fame
+3 more
OriginalEXE says

Fantastic work OriginalEXE! My only criticism would be that I don’t think the Font-Awesome shopping cart icon is very awesome at all :)
Thanks.

Not my favourite either. I used Glyphicons when started working on it for myself, but after I decided to share, it was no longer an option since it’s a premium icon set (but looks much much better).

But you are free to play with the looks :)

1484 posts
  • Has referred 1+ members
  • Has sold $10,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Made it to the Authors' Hall of Fame
+3 more
OriginalEXE says

Not sure if it’s something on my end, but just realised that any preview on mobile was sending to current_product preview while closing the frame. Left it empty and everything works fine.

Hey, on mobilephones I set redirection to direct demo because of the issue with iframes on idevices, check here: http://themeforest.net/forums/thread/switcheroo-open-source-item-switcher/111182?page=3#message_content_907622

1484 posts
  • Has referred 1+ members
  • Has sold $10,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Made it to the Authors' Hall of Fame
+3 more
OriginalEXE says

Great idea. Unfortunately it doesn’t seem to work as expected, as I get updates for all Item requests, not only on videohive, but for all marketplaces, although I put videohive.net in the link.
For Videohive forums threads only, use this: http://videohive.net/feeds/forums/videohive.atom

However, I was wondering if I can use something like that to tell me when there is a change in my item’s ratings. Like a rss-feed for my portfolio page…
You can’t use feed for that, you would either scrape the whole pages and regex the rating or maybe use Envato API if they return rating in the response.
1484 posts
  • Has referred 1+ members
  • Has sold $10,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Made it to the Authors' Hall of Fame
+3 more
OriginalEXE says
1484 posts
  • Has referred 1+ members
  • Has sold $10,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Made it to the Authors' Hall of Fame
+3 more
OriginalEXE says

We’ve started using this switcher also.

Awesome job guy, I really love the modification.

I’ll be optimising some stuff soon, after work calms down.

1484 posts
  • Has referred 1+ members
  • Has sold $10,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Made it to the Authors' Hall of Fame
+3 more
OriginalEXE says

I’m featured on CodeCanyon, yay! :)

1484 posts
  • Has referred 1+ members
  • Has sold $10,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Made it to the Authors' Hall of Fame
+3 more
OriginalEXE says



It sounds to me that you have to keep all your css in a single stylesheet, with the media queries in order.
Of course not, no one restricts you to the number of actual css files. It’s just a rule that if you have media-queries in css file, they should be grouped at the bottom.
Yeah I get that, what I meant was that the main stylesheet will need its relevant media queries in the same stylesheet, which means that under the guidelines the responsiveness can’t be easily removed from the DOM with JS, unless a different approach (@import) is used or there’s a nice little trick with JS that I am unaware of :)
You don’t have to do it like that.

Instead, have one separate css file for all responsive queries in your theme (could be little harder if you use css frameworks like bootstrap). That way it’s super easy to control things.

1484 posts
  • Has referred 1+ members
  • Has sold $10,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Made it to the Authors' Hall of Fame
+3 more
OriginalEXE says

It sounds to me that you have to keep all your css in a single stylesheet, with the media queries in order.

Of course not, no one restricts you to the number of actual css files. It’s just a rule that if you have media-queries in css file, they should be grouped at the bottom.

1484 posts
  • Has referred 1+ members
  • Has sold $10,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Made it to the Authors' Hall of Fame
+3 more
OriginalEXE says


Besides, “extra weight” argument makes no sense because options panel is only utilized in admin and only in case it’s actually visited, so there is no extra weight on actual theme performance.

Sorry, I don’t agree here, there was an author that recently said he couldn’t even get his theme to run through theme check properly because with hit option panel included it took 57 seconds, and without it took 14 seconds.

Speed in WP-Admin is just as important as speed on the front end, in the case of managing a large site and not just a simple blog, it’s extremely important :)

Though yes, you are correct, on the front-end there should be no detrimental effect to speed apart from more PHP for the server to parse, since it’s parsing the customisation API anyway regardless of whether you make use of it or not.

That makes no sense. I run Theme Check on a theme that definitely has larger code base than that of an author in question, and it’s finished in less that 10 seconds.

Speed in frontend is in no way affected (admin files are not even parsed, though parsing is not something you should be worried about considering the amount of code WP itself has, its ignorable).

Backend speed is also not affected, if things are done correctly. As stated previously, parsing practically does not affect the speed, and theme options panel is only generated on the panel page itself, which in my case executes as fast as standard wp settings page.

by
by
by
by
by
by