Maybe a solution is try something like this:
- Create a function that will run when theme is activated or when a Import Options button is used - Inside this, create a var that has your theme options array (try use get_option to get the array and a PHP debug function to get the values, for example) - Then, use the function update_option to change these values automatically.
It works with Options Framework, but don’t know about OptionTree. Probably the concept is the same.
Yeah, it’s how the things works here. I don’t know why disable without any alert, since bugs are normal in software, right?
I agree with the idea of charging a yearly price for updates and support – looks like is the trend to keep this kind of business working.
In the current way we need to always find new buyers – if we don’t release, we don’t earn too much (except if you are in Week Top Sellers) – this way we (authors) can’t just afford for updates and support because month after month the sales are becoming lower and lower but the tickets at support and update necessity keep normal or sometimes growing.
After a year of releases you’ll expend a lot of time updating and supporting items that already sold copies (let’s say 200 sales) – if each buyer pay 50% you’ll have about $3.5k ~ $4.5k back for you what can help the author keep updates and support.
The path we’re following will just saturate the marketplace with the same appearance files & old files that don’t worth support anymore.
Sure this should be added slowly, because the current way of business is too strong yet – but is something to keep in mind.
Great, standards are always great.
- Inadmissible shortcodes, all the listed ones can be added using a plugin, right?
- All HTML needs to be validated via the W3C validator. – will this be MANDATORY to whole theme? Sometimes at demo, you need use a style switcher, that usually will create warnings at validator, can you be more specific about validation, please?
- No inline styles are allowed any where – this means we can’t use style attribute or <style type=”text/css”></style> in our code, even when necessary? If we use a plugin to provide shortcodes, the plugin can add these inline styles, right?
- TGM Plugin Activation requires that the plugin stay inside theme folder? If we send the plugins (to shortcodes, portfolio and other things) in a separated folder and explain how to install the plugins that user want only – will we be rejected? Some plugins have 2MB or more, including inside theme folder would increase a lot theme package size, can you please clarify it?
All the best!
Amazing buddy! Congrats!
I remember when my brother thought it was something like Nutella and ate a full spoon LOL
We’re the team that take care about support of XiaoThemes, as @kriskork said, you would need contact us and to get fast help, open a ticket here https://xiaothemes.zendesk.com/home
Our e-mail inbox is really, really full everyday and only one guy check it – in our support center, you’ll have a team to take care of any issue
We’re waiting your ticket. Thank you.
Can you share your technique with us, other authors @webthemer ???
And of course, leave contact information
Welcome to the Jungle Hahahhaha
Well buddy, this is how the things work here… the best thing to do is keep releasing, with luck you’ll launch a best seller