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

Uninstall Weblinks #5903

Closed
coolman01 opened this issue Jan 28, 2015 · 13 comments
Closed

Uninstall Weblinks #5903

coolman01 opened this issue Jan 28, 2015 · 13 comments

Comments

@coolman01
Copy link

Steps to reproduce the issue

In extension manager uninstall weblinks

Expected result

All weblinks files (except search) unistalled

Actual result

Main files uninstalled, weblinks "package" not unistalled

System information (as much as possible)

PHP Built On Windows NT RESOLVE-2010 6.1 build 7601 (Windows 7 Business Edition Service Pack 1) i586
Database Version 5.5.32
Database Collation utf8_general_ci
PHP Version 5.4.19
Web Server Apache/2.4.4 (Win32) OpenSSL/0.9.8y PHP/5.4.19
WebServer to PHP Interface apache2handler
Joomla! Version Joomla! 3.4.0-beta1 Beta [ Ember ] 27-January-2015 20:00 GMT
Joomla! Platform Version Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT

Additional comments

@brianteeman
Copy link
Contributor

Was this a site you upgraded to 3.4beta 1 or a fresh install


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5903.

@coolman01
Copy link
Author

An Upgrade from 3.6

@brianteeman
Copy link
Contributor

Is this the error message that you get

Warning
Package Uninstall: Missing manifest file


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5903.

@coolman01
Copy link
Author

Yes

@brianteeman
Copy link
Contributor

Marking as confirmed


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5903.

@wilsonge
Copy link
Contributor

Raising priority to urgent so it is a blocker for 3.4. Should be fixed before RC.


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5903.

@mbabker
Copy link
Contributor

mbabker commented Jan 28, 2015

Anyone care to take a guess why this check is saying the weblinks.php file doesn't exist (which is how the package manifest would be removed)? And yes, the package manifest is in the update package.

@wilsonge
Copy link
Contributor

@mbabker isn't that check for when we are updating the CMS and won't get called when you uninstall weblinks through extension manager after updating to beta?

@mbabker
Copy link
Contributor

mbabker commented Jan 29, 2015

The issue is the manifest is not present, hence the error message @brianteeman posted. I did a test update on a local 3.3.6 install and found that the manifest was not in place. The only possible ways for that to happen is the file not included in the package or the file being deleted by the update script.

@mbabker
Copy link
Contributor

mbabker commented Jan 29, 2015

Making things more intriguing, I've tested 2 updates via the update component and both of those don't place the weblinks manifest in the filesystem. I tried an update through the Extension Manager's Install from URL option and it showed up.

@mbabker
Copy link
Contributor

mbabker commented Feb 11, 2015

I just realized why this is failing. The update server is serving the Full install package versus the update package. The full package doesn't have the weblinks package manifest since weblinks isn't installed for new installations.

@mbabker
Copy link
Contributor

mbabker commented Feb 11, 2015

The update server has been updated to serve the update package now versus the full package. Please test updates and uninstalling weblinks now.

When updating, please ensure the package URL displayed on the update screen indicates it is the update package. If it still says full, your site is pulling from a CDN node that has not yet refreshed.

@infograf768
Copy link
Member

@test

Works fine now.
Remains to get it on JED.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants