[#6015] - Error message installing a library using "discover"
- Closed
- 29 May 2017
- Medium
- Build: master
- # 6015
When installing a library using the "discover" function, it returns:
JFolder: :files: Path is not a folder. Path: /var/www/joomla/3.4/libraries/3.4
JFolder: :files: Path is not a folder. Path: /var/www/joomla/3.4/libraries/3.4
JInstaller: :Install: Can't find XML setup file.
The problem is located in JInstallerAdapterLibrary::getElement()
where $this->parent->getPath('manifest') evaluates to null.
As a consequence, $manifestPath contains the libraries directory, rather than the name of the xml library file.
The subsequent statement which is supposed to get the file name of the xml without the .xml extension returns the name of the libraries directory instead.
$element = preg_replace('/.xml/', '', basename($manifestPath));
== Replicate the problem ==
Just install a library using discover feature.
Votes
joomla-cms-bot
- | Labels |
Added:
?
|
||
zero-24
- | Milestone |
Added: |
||
The error is happening in loadLanguage because none of the paths are set at that point (the prepareDiscoverInstall doesn't get called to register paths until after the loadLanguage call). So, need to do some tweaking here.
| Category | ⇒ | Libraries |
Something similar when installing and removing extensions of type='file'.
Installer (after J!3.4) writes in DB -> table '_extensions' -> column 'element' the value of tag instead of the manifest file name as before.
(Column 'name' is also populated with tag from manifest file.)
The problem comes when you try to remove this extension.
Joomla is looking for manifest file named 'value-of-the-element-field.xml', and throws error since there is no such file.
Is that a new approach in JInstaller, or simply a bug?
I wanted to make a new ticket here, but found this very similar issue.
Hope somebody answer here.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/6015.
+1 (For me, the cause behind the error turned out to be badly-formed XML. A nicer error message would have been handy.)
@mbabker reminder as @wilsonge tagged you
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/6015.
If it's decided the continued standardization of JInstallerAdapter paths
isn't breaking anymore B/C (the changes in 3.4 did so), I can work on
finishing it probably for 3.6. Otherwise, not fixable before 4.0.
On Thursday, March 10, 2016, Brian Teeman notifications@github.com wrote:
@mbabker https://github.com/mbabker reminder as @wilsonge
https://github.com/wilsonge tagged you
This comment was created with the J!Tracker Application
https://github.com/joomla/jissues at issues.joomla.org/joomla-cms/6015
https://issues.joomla.org/tracker/joomla-cms/6015.—
Reply to this email directly or view it on GitHub
#6015 (comment).
| Status | New | ⇒ | Needs Review |
Set to Needs Review based on @mbabker question above
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/6015.
| Milestone |
Added: |
||
| Status | Needs Review | ⇒ | Confirmed |
| Labels |
Added:
?
|
||
| Milestone |
Added: |
||
@demis-palma Thank you for creating this. At this time it can not be accepted as it would break our backwards compatibility promise but I am marking this to be re-evaluated for Version 4 which is the next release where we can make these breaking changes.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/6015.
| Status | Confirmed | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-05-29 17:50:37 |
| Closed_By | ⇒ | brianteeman |
@mbabker One for you to look at