If you watched this video, please check it on your forum and vote in the poll.

carefully look at the situation in which the widget disappears,

bugs will appear when you rearrange the widget between areas and return with the widget to the previous area it was placed in.

example:

from areaHeader to areaSidebar, you save, ok its work.

but when you move from areaHeader to areaSidebar and you decide back to areaHeader and you save it, the widget doesn't save the position and disappear,

this bug is attending in all areas and applications.

 

Where is the solution?

core/modules/front/system > widgets.php
cms/modules/front/pages > builder.php - for those who use IP.Content App

the problem is mainly related to the above two files,

both have a function:

	/**
	 * Reorder Blocks
	 *
	 * @return	void
	 */
	protected function saveOrder()
	{
	...
	}

it lacks a function that would check in which area the widget is actually located or the current function is blocked in a situation when the widget is moved between areas several times and will be placed in the previous area.

it is possible that these functions are also affected:

	/**
	 * Get Configuration
	 *
	 * @return	void
	 */
	protected function getConfiguration()
	{
	...
	}

or

	/**
	 * Get Output For Adding A New Block
	 *
	 * @return	void
	 */
	protected function getBlock()
	{	
	...
	}

I'm not a programmer, I just found where the problem is, the rest is up to you what you do with it.

Thank you for your attention 😇

I am unable to replicate what you are seeing there. What browser is it that you are using?

I caught this bug on chrome, firefox, and opera, I have the latest version 4.6.9 updated a few days ago,

and I checked it on another installation on localhost and this bug can also be done there 🙄

Ah, it actually only seems to be with that block for some reason.

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.

 

I have closed the poll as the bug is confirmed

This should now be working on the latest version. Please let us know if you have any further issues