Posts by uDesignStudios

The dev half of uDesignStudios humbly submits the youngster mo

http://dl.dropbox.com/u/2571167/mo_slower.gif

Hey all!

I know what happened to SalesDonkey! My iOS dev program ran out and due an issue on my part I haven’t managed to extend it. This is why it is no longer in the AppStore. No worries though, I’m working on it, it should be back in there I guess around Wednesday if everything goes ok…

In the meantime we’ve been working on the Desktop version, if anybody wanted to test that, just drop us a line via the contact form

UDS

Very nice!

Also, I wanted to ask if there are any plans on implementing paged statements API . I would really like this for SalesDonkey.

UDS

Hey!

I’ll post this here too, since this thread looks livelier than mine (http://codecanyon.net/forums/thread/plugin-updates/49970), I hope you don’t mind

I took the liberty of updating this, in order to handle multiple scripts using it. So if we start using this we won’t get errors when users use more than one update-notifier-enabled plugin

You can find the code here: https://github.com/meosoft/WordPress-Plugin-Update-Notifier-for-Code-Canyon

It uses PHP variables instead of constants and all functions are guarded by a constant, so you don’t get function already defined errors. It also puts all plugins in one place, so you’ll get only one menu entry that notifies you about the updates.

Please let me know what you think

mordauk said
Hey guys, since we have no idea of when the official option for this is going to be available, I’ve gone ahead and finished the one I was working on. It’s actually a fork of the theme update notifier script written by Unisphere, but adapted to work with plugins. I’ve created a forum topic for it here: http://codecanyon.net/forums/thread/a-wordpress-plugin-update-notifier-script/50850

Good Idea Mordauk!

I elaborated on it a bit and here’s my updated version: https://github.com/meosoft/WordPress-Plugin-Update-Notifier-for-Code-Canyon

It has support for multiple plugins, so if, say, two of my plugins and one your plugin use the same basic script it should not produce errors. I also updated some other small things like, for example I changed the cache to use WP’s Transient APIs.. I can send you pull request if you want .

Anyway hope you’ll like it

maxvarlson said

Mocarg said
Europe europe europe…

+1

+1

Great to hear that Jeffrey!

Looking forward to seeing that in action. If there’s need for beta-testers or even developers, feel free to contact us, we’ll be more than glad to help.

UDS

– other plugin loading custom script into our plugin admin page

that indeed is a problem, but it is one that can be easily avoided, without any compromise, from the plugin author’s side. You just need the proper hooks, that’s all.

But there can be legitimate reasons to deregister the default jQuery. For some plugins with heavy JS use, new jQuery features and speed improvements can really make a difference. And I’m not even talking about jQuery bugs, this was especially apparent in WP 3 .1 and before. WP included jQuery 1.4 when 1.5 and 1.6 has been already out, so why you shouldn’t be able to update to the newer jQuery when it provides better functionality and fixes to some important bugs? And the old jQuery is the only thing preventing your plugin from running on WP 3 .1 and lower?

All I’m saying is that if you write your code defensively and make sure it is compatible with the latest version, which it should be anyway, there can be no conflicts if a plugin registers the newer jQuery. And from my experience as plugin and theme author I can only confirm this.

I can understand your frustration, but not everything is black&white. That’s all I’m trying to say. I’ll even go so far as to say that for 95% of the plugins you are completely right and they should not deregister the default jQuery. But there is that 5% that should have the ability to do so if it is done responsibly.

OK, first of all, we’ve decided to do this based on our experience. This is ultimately less work for the customer, because, if any, he has to do some work when setting up his website and not after each update, secondly an updated version of a plugin distributed via CC takes time (could be weeks) before the customer is installs it. And lastly, we’ve had very little to no reports related to jQuery version conflicts. We’ve had conflicts with other libraries like Prototype, or conflicts related to themes that include jQuery directly in header.php rather than by the WP queue mechanism.

I agree that deregistering jQuery is a dirty solution, and I’m glad a debate has been started on this issue. I’m just trying to add a practical viewpoint from our experience.

Hi all,

we’ve been asked recently by several people why is it that our WordPress plugins do not appear in the updates. We told them that it is because they are not distributed through the WP plugin directory which handles this automatically. I would like to solve this problem though.

Problem: How to enable autoupdate for your WP plugin or theme in a way that would be both easy to use for the customer and yet would prevent unauthorized copying.

I know there are brilliant minds in this community, that could help out.

My idea is that we could create either a separate WP plugin that would take care of every item installed from the marketplaces with a simple hook or interface that would enable plugin and theme authors to join, or a framework that people could embed into their themes or plugins.

I would like to this to be open source, so we could all benefit, something like OptionTree, so I’m thinking a repo on GitHub? I’m also willing to invest my own time and energy into this for the community.

The only thing that seems to be problematic so far is the mechanism for authentification, I think we might need some help with that from Envato. Some of this can be achieved via the API right now, but I don’t think that would be the ultimate solution. Until we get proper support from Envato we can develop an earlier version of this, that would only notify the user that the update is available.

Please let me know what do you think, or if you are interested in helping me out. I would also like to hear from Envato staff if this is something that they would be willing/able to help us with.

UDS