@remotehelp can you try to explain a bit more how you can reprouce the error? Automatic update using the Joomla update component? Or manually update? is the file /public_html/administrator/manifests/libraries/phpmailer.xml there or not?

wasnt that file moved

On 30 March 2015 at 22:47, zero-24 notifications@github.com wrote:

@remotehelp https://github.com/remotehelp can you try to explain a bit
more how you can reprouce the error? Aotomatic update useing the Joomla
update component? Or manually update? is the file

/public_html/administrator/manifests/libraries/phpmailer.xml there or not?

This comment was created with the J!Tracker Application
https://github.com/joomla/jissues at issues.joomla.org/joomla-cms/6611
http://issues.joomla.org/tracker/joomla-cms/6611.

—
Reply to this email directly or view it on GitHub
#6611 (comment).

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

hmm still here: https://github.com/joomla/joomla-cms/blob/staging/administrator/manifests/libraries/phpass.xml Or i missunderstand you? @brianteeman

PHPMailer is uninstalled as an extension between 3.3 and 3.4 in favor of the Composer integration. So the manifest is deleted.

that is phpass not phpmailer

On 30 March 2015 at 22:53, zero-24 notifications@github.com wrote:

hmm still here:
https://github.com/joomla/joomla-cms/blob/staging/administrator/manifests/libraries/phpass.xml
Or i missunderstand you? @brianteeman https://github.com/brianteeman

—
Reply to this email directly or view it on GitHub
#6611 (comment).

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

Woops wrong file. Yes you are right @brianteeman

phpmailer not phpass PHPMailer is moved correct! https://github.com/joomla/joomla-cms/tree/staging/libraries/vendor/phpmailer/phpmailer

@zero-24 manually update Joomla_3.4.x_to_3.4.1-Stable-Patch_Package.zip ... is not file and not dir :) /public_html/administrator/manifests/libraries/phpmailer.xml no !isset()

...but if try again install Joomla_3.4.x_to_3.4.1-Stable-Patch_Package.zip then I again get:

Warning: simplexml_load_file(): I/O warning

Please explain what you mean by "manually update"

@brianteeman you are noob?:) Select and upload Joomla_3.4.x_to_3.4.1-Stable-Patch_Package.zip ... and install through Joomla installer ... of course :)

I am not a mind reader

On 31 March 2015 at 09:29, remoteshaman.com notifications@github.com
wrote:

@ brianteeman you are noob?:) Select and upload
Joomla_3.4.x_to_3.4.1-Stable-Patch_Package.zip ... and install through
Joomla installer ... of course :)

—
Reply to this email directly or view it on GitHub
#6611 (comment).

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

The installation using Extension manager -> Install is NOT considered "manually update". Manual update is known as extracting the distribution and replacing the files using a filemanager. Used at a time when updating wasn't as complex as it is now. Today you need to do a lot more to manually update.

Guess that takes care of who is the noob here!

@sovainfo - another noob?:) logically, if I extracting the distribution and replacing the files using a filemanager then from where I get "Warning: simplexml_load_file(): I/O warning"?

I mean auto update if patch load and install trough "Extension manager - Update - Find update - Install", - although Auto Update this in Windows :)...

If trough "Extension manager -> Install" is NOT considered "auto update" as is and "Extension manager - Update - Find update - Install", and at least semi-manual! :)

Ok, I noob, and you also ;), but warning still exist.

You obviously had a failed update getting to 3.4. As part of the 3.4 update, the PHPMailer manifest was removed from the filesystem and the extension entry in the database deleted. For you to be receiving this error message indicates that the extension is still in the database. This can be confirmed via the Extension Manager's Manage view; filter for PHPMailer.

@mbabker Thanks!

I removed the record from the database DELETE FROM "xxx_db"."xxx_extensions" WHERE "xxx_extensions"."name" = "PHPMailer" and warning disappeared.