Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Feature (was Develop) #351

Closed
wants to merge 31 commits into from
Closed

Update Feature (was Develop) #351

wants to merge 31 commits into from

Conversation

swiderski
Copy link

Update feature!
Hopefully this time I will do it right.

duckzland and others added 30 commits July 13, 2014 09:02
The initial attempt is still crude hack to add plugin updating ability to the bulk table form. Needs more work to add better messages for updating and things such as putting to maintenance mode first, implements the Plugin_Upgrader class actions and filters.

Need more testing if this will work on every possible servers.
Added plugin version check when attempted to force activate a plugin, only activate if the version is higher than the registry.
fix esc url causing broken link, need testing!
merging develop with mainstream
@duckzland
Copy link

Hi guys, is this going to be implemented anytime soon? Thanks

@GaryJones
Copy link
Member

@jrfnl has looked through the code, but found several issues with it:

  • bulk update on installed plugin without update will re-install
  • pre-packaged update via link, says the plugin has updated, but in reality it hasn't
  • repo found updates are not shown nor taken into account

So, yes, while this feature will probably get into the 2.5.0 release, it needs implementing properly in a way that we'd be happy.

This ticket will be closed once the new PR has been created.

@duckzland
Copy link

ok thanks for the info, and I think at this rate its better if you develop your own version on how to update this plugin. it is a nightmare to keep up with the mainstream repo

@jrfnl
Copy link
Contributor

jrfnl commented Apr 28, 2015

@duckzland I'm working on integrating your code and have just send in #368 to actually make integrating the update feature a lot simpler - with graceful thanks for all the hard work you've done on this!

@duckzland
Copy link

@jrfnl If possible you could take a look at my master branch, I've clean out a bit the code and now the updating and install will have 2 different set of page, each page will list only plugin related to be updated and / or installed. I really believe at this development pace, it is better if the collaborator to do the integration, will result in much cleaner code imo.

@jrfnl
Copy link
Contributor

jrfnl commented Apr 28, 2015

@duckzland I will - I've got your fork as one of the remotes for my local version atm ;-)

@swiderski
Copy link
Author

@duckzland - so is there any help needed any more, or now we just wait?

@GaryJones
Copy link
Member

Just wait :-) #368 is going in shortly, followed by some abstraction-related PRs to reduce duplicate code, then we have a cleaner code base to add new features like updates :-)

@GaryJones GaryJones changed the title Develop Update Feature (was Develop) Apr 28, 2015
@duckzland
Copy link

@swiderski I think just as gary said, better wait till the chaos finish and we can try to test and sort out bugs :)

@jrfnl
Copy link
Contributor

jrfnl commented Apr 28, 2015

@duckzland @swiderski With a bit of luck, I'll have something for you to test some time tomorrow. Fingers crossed.

@jrfnl
Copy link
Contributor

jrfnl commented Apr 29, 2015

now the updating and install will have 2 different set of page, each page will list only plugin related to be updated and / or installed.

@duckzland Where can I find that code ? I've done compares based on Duckzland-update-branch/add_update_mode and on https://github.com/duckzland/TGM-Plugin-Activation/commit/abc28dbcfb04bb8fc1fdc53c11c00ef6750aa5de which is the last usable one I can do a compare on.
In the next commit you seem to have changed the code style completely away from the WordPress standard which makes a compare impossible, let alone any possibility of future merges.

@duckzland
Copy link

@jrfnl it is in the master branch the add_update_mode is based on the 2.4.x branch while the master branch is based on the 2.5.x branch. You can use PHPStorm IDE with compare with clipboard function it should easen the comparison.

@jrfnl
Copy link
Contributor

jrfnl commented Apr 29, 2015

@duckzland Will have a look, but seriously - why make it so difficult ?

@duckzland
Copy link

@jrfnl sorry wasnt intended to make things difficult for you.

@jrfnl
Copy link
Contributor

jrfnl commented Apr 29, 2015

@duckzland not just me, you're going to have a hell of a job if you ever want to be able to pull the changes from this plugin into your fork again.

@duckzland
Copy link

@jrfnl oh this fork is temporary fix only since I got themes that need to be released asap, once you got this feature in mainstream I'm going to remove the fork :) no need for forking if mainstream has it.

@swiderski
Copy link
Author

IF you like I can make some merge and switching back to proper Wordpress coding style. It wont take more then 10 minutes with PHPStorm. Just tell me what you need exactly.

@duckzland
Copy link

@swiderski its cool by me :) maybe create a new branch based on master? or you can coordinate with jrfnl for whatever best for her :)

@jrfnl
Copy link
Contributor

jrfnl commented Apr 30, 2015

@swiderski Don't bother. I'm implementing that bit quite differently anyhow. $mode is only available since 4.1 and I don't see any need to make the minimum requirement for TGMPA WP 4.1 at this moment.

@jrfnl jrfnl mentioned this pull request May 3, 2015
@GaryJones
Copy link
Member

A version has been merged into the develop branch. See #381.

@GaryJones GaryJones closed this May 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants