No ideas?

if you give more System Information maybe someone can help easier if its a Core issue – also you have asked in forums?

Hello,

if you create a new menu item and select published on save what happens?

Can you provide a screencast of the issue?

@sinasafarnezhadian Please run this query
SELECTpublishedFROM#menuWHEREalias= 'root';
Replace # with table prefix
@franz-wohlkoenig This can be a good test for #15806

@tonypartridge

it always switched to trash/paper bin (I dont know the right term).
Here is a screencast:
https://we.tl/vesdnZetkt
I cannot upload it here :/

@wojsmol

I will try it today.

Thank You

@sinasafarnezhadian Please post result of this query here.

@wojsmol here the result as img

@sinasafarnezhadian If you have backup before update then plase test #15806. On custom update serwer content 3.7.0 width #15806 appyled. So after test you must chene update server to defout and update to 3.7.1.

what if there is no Back up ? :)
Or the back up is no more up-to-date

Then an update shouldn't have been preformed.

On 22 May 2017, 15:46 +0100, sinasafarnezhadian notifications@github.com, wrote:

what if there is no Back up ? :)
Or the back up is no more up-to-date

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (#16066 (comment)), or mute the thread (https://github.com/notifications/unsubscribe-auth/ABVgllDjxvabPV7Mg99KxU6XBpLpGD72ks5r8Z-qgaJpZM4NdlTk).

@sinasafarnezhadian Then run this queries

UPDATE `#__menu` SET `published` = 1 WHERE `alias` = 'root';
UPDATE `#__categories` SET `published` = 1 WHERE `alias` = 'root';

replace #__ with database prefix then publish menuotems manuali
If you woth help with testing #15806 then restore even old backup locally run query from #16066 (comment) if result is rhe same as in #16066 (comment) then test PR on this backup.

@wojsmol thx for helping
UPDATE #__menu SET published = 1 WHERE alias = 'root';
that helps me.

I will test the old back up, as soon as I restore it.

I am closing this at this time - it can be opened if required but this does sound like a support issue for the forum and not a general bug for the tracker

In addition, the issue was fixed by PR #15806