User tests: Successful: Unsuccessful:
Pull Request for Issue # .
dotenv that is required for the abovenpm ci, npm run build:com_media and npm run build:com_media:dev and verify that media manager works on all of themjoomla.mediamanagerPlease select:
Documentation link for docs.joomla.org:
No documentation changes for docs.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed
The new command is documented in the build/README.md
| Category | ⇒ | JavaScript Administration com_media NPM Change Repository |
| Status | New | ⇒ | Pending |
| Labels |
Added:
NPM Resource Changed
?
|
||
I have tested this item
I was not sure about the sequence to apply the npm commands - but the media manager worked after npm ci and after npm ci + both others. I could see local session change as different folders were selected. The full image folder opened either with the folder containing the existing image or with the folder from the session storage - is that right. Complicated, but I could not see anything wrong.
@ceford thanks for testing this.
Complicated,
Yeah it's weird but somehow we needed to keep in memory the state of the last visited folder and localSession was a good solution. FWIW I'm not changing anything in the logic of the media manager here, I'm just swapping a plugin for another one
I have tested this item
| Status | Pending | ⇒ | Ready to Commit |
RTC
| Labels |
Added:
?
|
||
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-12-28 17:39:37 |
| Closed_By | ⇒ | wilsonge |
We definitely need to swap the persistence plugin out. I also think @laoneo probably should give this a good test against DP Media :)