We are having problem with the old API as well. Many of our customers are raising questions…Does anyone have a fix?
“Operation timed out after 5001 milliseconds with 0 bytes received”
Our demo server is under affected by a kind of malware which Suciri calls “Pseudo darkleech”: https://blog.sucuri.net/2015/03/pseudo-darkleech-server-root-infection.html
The evidence is the same as described in the post above: /wp-includes/nav-menu.php is injected and .htaccess is re-written everytime. As a result, home page works fine but not other pages (which uses URL friendly)
I have update all plugins to latest version, restore original WordPress files. However, the infection is still there. (It comes back after few days).
Does anyone know about this? Do you have a fix?
Sorry to be such a pain, but it’s been almost a week and we still didn’t get any official response to this thread.
Will something change regarding the review process in the the close future or should we be afraid to take weekends off or go on holidays?We’re all waiting for your answers. Thank you.
I agree, Envato should have better process for soft-disabling items. I just have my own item (with more than 1800 sales) disabled yesterday and have not received any notifications from Envato and still waiting for market support. Not a happy day.
Today, I am noticed that my item GamePlan has gone disappear in the listing page. That means: People can not see the item in my portfolio page: http://themeforest.net/user/cactusthemes/portfolio . And my item is not shown in the search result page (even if the search term is “gameplan”)
Please, anyone had or is experiencing the same issue?
Thank you CactusThemes
There’s this article http://nvie.com/posts/a-successful-git-branching-model/ that talks about one approach, but could be overkill for smaller projects/teams.
What I’d do is keep most of your development on master, then have a branch for each release you need to maintain. To release a new version, you branch from master again. Any fixes for older versions get cherry-picked from master, or made in the branch directly if they’re only applicable there.You could also look at using feature branches and pull requests depending on how big your team is, and how much co-ordination and/or code-review you want to use.
Thanks for a very detailed answer