Radu,
You had gotten the last version of the theme pretty polished. Before releasing a new version to theme forest why not start a private and public beta?
The issue with this release is rather major. Users that aren’t an administrator cannot modify any interfaces or even set their own post options. Simple drop down menus in the back end are broken. This should not be happening.
Plus the Speed Booster plugin is also broken. It stops the search function from loading on a page.
On one side, I agree with the beta-stage but…… when the former version was working good for you, you could just have waited a few days to see the reactions to the v3 and possible bugs. Then you would have saved yourself the trouble because you could just wait for the 3.1 release with less bugs – I’m sure no one forced you to upgrade to v3 🙂
Oh no don’t get me wrong… livingsmarttv, your recommended process is usually what I follow. The issue is, it’s improper to release the code to production (i.e. for “SALE”) on Themeforest when these sorts of bugs have not been ironed out.
This is why RADU should have a beta test group that includes users like ourselves who can test for this functionality.
Remember that anyone buying the theme from Themeforest right now is getting broken code and they have no fallback unless RADU sends them an older version of the code. Why bother with that hassle when a closed beta group can sniff out this stuff quickly and discreetly?
I want to report another bug (since I’m not sure where to report them directly) with v 3.0, the h1 title from the individual posts, kinda screws up when hovering with the mouse or when hovering the menu above. I’ve tested this in the previous 2.x versions, there’s no problem there. The bug isn’t major, I think it’s a rendering issue of sorts, I’m not sure.
Hello,
the two most serious bug are fixed now and I will update the theme on themeforest in a couple of hours after we finish testing.
I too think it would be nice to have a beta group/program or early access to the latest theme code but we don’t have the logistics for this yet.
1. The first bug (speed booster) – was because our deploy script did not include two new javascript files in the theme (the minimize ones). All of our testing with the speed booster plugin took place with our local version of the theme, not the final deploy broken version. (From now on we will test all things on the final deploy version)
2. the second bug with the authors that are not admin was due to a missing en queue for the wordpress color picker. For some reason it is not automatically loaded when a user is not admin. (All of our test users where admins 😐 )
@vexx can you give me a sample url? It is happening also on our demo? What browser?
Thanks for the feedback
Well, I can’t give you an example since I reverted back to 2.x. I have a bunch of authors that write articles and I couldn’t leave the site to 3.0 until you guys fixed it. Once I upgrade to 3.0 again, I’ll be happy to provide you with a link.
Also Radu, is it possible that after you guys reupload the fixed theme, to tell us which were the fixed modifications? I already customized my 3.0 theme last night (there were some things incompatible with 2.x and I had to redo them) and I hate to do that again..it’s easier for me to add the code or reupload certain fixed files.
Thanks!
Hey Radu,
Thanks for getting this fixed quickly. My team and I will gladly support you with beta testing when ever you are setup to do so. We have a test environment we can load code into that is a mirror of production so the testing can be pretty concise.
Best of luck with the rest of your updates and I look forward to more from you.
Best Regards,
Luca