Christiane62 said
Hi, I have installed ‘Xero’ template and now I’m having trouble, uploading images to the slider.
My WizyPanel looks completely different to the one in the documentation. Which wouldn’t be a problem if only it would work. If I click on ‘upload’ under Slidemanager, it only takes me to the top of the page, nothing Happens, no upload is possible.
Can someone help me?

Hi Chris,

Unfortunately, the WizyPanel included with Xero theme works with the latest version of WordPress just fine. However, I understand that conflicts with plugins and so may cause problems with the theme.

As this is not the appropriate place to discuss theme issues, I would ask you to email me directly through my profile page and I will handle the issue ASAP .

However, if you are talking about the slider manager, thats a different story. If you look into my Tuts+ Marketplace portfolio you will find a tutorial which gets you started with a basic slider manager

wizylabs said
Hmm nice idea, but again its almost impossible to protect your code completely! Maybe a better idea would be a multisite for your theme, on your own server, that allows users to create a new instance of the theme with their own username/pass etc.. then you have full control of what they see as new users (theme instances, ie sites) created can be limited to certain capabilities etc…

I agree about code protection, in fact the main goal of this post is to find (if any) the best way to achieve this. I mean, not everybody is skilled enough to clean the code from the protections… only advanced users could be able to achieve so.

A multisite installation is also a good idea… but correct me if I’m wrong. You, as admin of the network, would need to create each theme installation manually for each user asking for a demo, right?

not really, everything can be done programmatically in WordPress. You can prepare a landing page for your network site that has a register form for users seeking demos etc…

It wont be hard, you can even require a envato api to make sure that the user is from envato and can chase him up later on!

Hmm nice idea, but again its almost impossible to protect your code completely! Maybe a better idea would be a multisite for your theme, on your own server, that allows users to create a new instance of the theme with their own username/pass etc.. then you have full control of what they see as new users (theme instances, ie sites) created can be limited to certain capabilities etc…