Go to modules
edit previously created module that was assigned to a template position
try to delete the position so the module can be used as an instance in a page or template instead of in a position
the position bar will have an X on it allowing you to reset it to none
This is not there in the latest upgrade, see screenshot
Joomla 3.6.5
this is required when clients want to rearrange their website and move modules to different places/functionalities
As a custom web designer, I am moving modules around all the time and sometimes they need to be removed from a position and added to a menu or embedded in a page or module instance instead after review of initial setup
Currently I have to delete the module and recreate it and this can be time consuming when it requires extensive configuration
If I knew what staging was, I could attempt to verify :).
However I don't.
I am using a live site which is fully delegated sitting on a commercial shared hosting server using Joomla 3.6.5
The is no delete button (X) on the position dropdown in modules
Unfortunately, in the commercial environment, clients want changes to templates on the fly after the sites are launched and sometimes you need to amend the position to zero on a live site
If you could tell me about staging, I will look at that
Thanks
Jacqui
Staging is the current developing code here in this repo. There is a download button on https://github.com/joomla/joomla-cms which gets you the current developing version. It can be installed like a regular package you download from www.joomla.org.
I can confirm this bug - for 3.6.4 too. In 3.7 dev it is fixed.
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-12-17 16:45:55 |
Closed_By | ⇒ | Bakual |
Closing as it is fixed in staging as expected.
Thanks guys nice to know it is fixed, will await the rollout and then stop muttering to myself when I am playing with modules :)
bug returned in 3.9.0
The is no delete button (X)
in HTML I have see:
"allow_single_deselect":true
but is no X button
I think there is already an issue open about this. But anyway - commenting on closed issues will not get anything solved. You need to open a new one.
That should be fixed in staging. Can you verify?