Here are a couple of things that bug me:
- The next & prev arrows on the slier aren’t very attractive
- The read more buttons are hard to read
- There is a feeling of inconsitency in the graphic elements. For example the sidebar widget boxes have a feeling of 3d and layering, but everything else is extremely flat. There are also at least 4 styles of icons, bullets etc.
I know the WordPress Aid by theMolitor is WPML compatible:http://themeforest.net/item/wordpress-aid-charity-blog-theme/238405
You can share the averages with us too after you compile the data.
August 19th is my birthday too
I just came back from a wonderful trip around south-eastern Europe:
Zagreb – Gratz – Wienna – Munich – Basel – Geneva – Milano – Ljubljana – Beograd – Sofia
It was one of the best experiences ever
I’m not sure if anyone brought this up but what about a lil’ something for the “elite” buyers
Well, from what I’ve read the review process of the WordPress Theme Review team takes several hours per theme so I don’t think that is the case
I think you are allowed to do that, after all it’s GPL licensed code.
Most of the time you won’t have any problems just placing the plugin’s files in your themes folder for example in a “functions/plugins/” folder and then including the main plugin file from your functions.php. I’ve done this several times and here are some tips:
1. Never keep a copy of the plugin in the wp-content/plugins/ folder.
Sometimes when the plugin is more complex it may include some files by calling them trough the plugin api which means that it will load the files in the wp-content/plugins/plugin-name folder. By not keeping a copy of the plugin there you would generate php errors and you can go trough the code and fix that by calling your copies of the files.
2. Check for namespacing and translation issues. Sometimes the plugins will use a different namespace than your theme.
3. Always check with the author of the plugin if he is ok to incorporate his plugin in your theme. It’s not against the law but some may not be content with it and it wouldn’t be a friendly thing to do.
4. Make sure you know the code of the plugin inside out as you will need to support it if you integrate it rather than suggesting your customers to install it themselves.
5. First buy a regular license and try to integrate the plugin and then buy the extended one as some plugins are too much of a hassle to integrate to be worth it. You better find alternatives in this case.