User tests: Successful: Unsuccessful:
Pull Request for Issue # .
Please 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
| Status | New | ⇒ | Pending |
| Category | ⇒ | Unit Tests Repository Administration com_admin com_banners com_categories com_config com_contact com_content com_contenthistory com_finder com_installer |
the day when I'll understand, this "fast moving target"...
is plugin covered with these strict b/c policies ?
just think about it.
moving would mean that something that currently happens by default with no user intervention will stop working and a user will need to setup and configure something that they never had to do before
| Category | Unit Tests Repository Administration com_admin com_banners com_categories com_config com_contact com_content com_contenthistory com_finder com_installer | ⇒ | Administration JavaScript Repository NPM Change com_tags Front End Libraries |
| Labels |
Added:
?
PR-4.3-dev
|
||
if i was writing this then I would be copying to the the scheduler AND adding an instruction in the scheduler to disable the automatic process in the plugin.
i'll redo with the add instead of move
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2023-05-01 10:30:40 |
| Closed_By | ⇒ | alikon | |
| Labels |
Added:
NPM Resource Changed
PR-4.4-dev
Removed: ? |
||
I can see what you are trying to do here. For b/c you cannot move2shceduler but you can add2scheduler