-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wordpress 6.6 makes opening of subpages in Menu1 impossible #4
Comments
@extremecarver Do you get a corresponding error displayed which can lead us to a solution for that issue? |
No nothing in console. Error not happening to your site(s)? |
I haven't updated yet to that WP version for the site i use Atahualpa. |
Ah okay, I have no clue how to investigate it as I see no errors. But I can just not update wordpress for a couple of weeks |
Perhaps the release notes for version 6.6 could give a hint... |
Performance updates That's not telling much |
But we could have a look in the list of changed files (mainly menu related) what has changed there. |
Above my knowledge of php. Seems only elemontor has a similar problem: https://wordpress.org/support/topic/wordpress-6-6-header-dropdown-menu-fail/ |
That's very strange, I tried with all plugins deactivated. Which php
version are you using?
…On Tue, 23 Jul 2024, 15:28 Valentin Treu, ***@***.***> wrote:
I've just updated to Wordpress 6.6 on a local Docker installation for the
homepage i support, and don't encounter the problem you mentioned, i.e.
submenu items do show up and are clickable:
Screenshot.2024-07-23.at.15.22.47.png (view on web)
<https://github.com/user-attachments/assets/ba13d5c3-6978-4575-8b35-0da447a7caf4>
—
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACBBDGJAJFB7WY62W4AWS3ZNZK7JAVCNFSM6AAAAABLEMN5WGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBVGI2TOMBZGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Docker logs say 8.0.28 |
We have got the same problem with our page |
Which php version do both of you use? I will then try to install a wordpress image with that php version and see if i can reproduce the problem. |
I use 8.2, 8.0 isn't supported anymore. With nginx
…On Thu, 25 Jul 2024, 16:50 Valentin Treu, ***@***.***> wrote:
Which php version do both of you use? I will then try to install a
wordpress image with that php version and see if i can reproduce the
problem.
—
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACBBDBBTPDKHSJNEEUZZWDZOEGD7AVCNFSM6AAAAABLEMN5WGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJQGU2DMMRSHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I was able to run the homepage in another Docker container under php 8.3.9, and the (sub)menus work fine there too. |
And could you also update to Wordpress version 6.6.1 and verify if the problem still exists? |
Not really,
Border:solid 3px #FFFFFF
Font size: 1.3em Arial, sans-serif
Width, 22
Otherwise all default except colour which should not matter
And yeah - gave it another try on 6.6.1 and it's still the same.
…On Thu, 25 Jul 2024, 22:07 Valentin Treu, ***@***.***> wrote:
I was able to run the homepage in another Docker container under php
8.3.9, and the (sub)menus work fine there too.
Could it be that you guys have special settings for Menu1 in
Design->Atahualpa Theme Options which make submenus don't work correctly
anymore?
—
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACBBDDEFCJ4QJ6YQC2F6UTZOFLGZAVCNFSM6AAAAABLEMN5WGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJRGMYDONJVGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
ata-openmtbmaporg-20240725.txt Here are my full theme options. But somehow I don't think they are the problem. I kinda defaulted everything and it was still the same (the delete bfa4 key option didn't work and I was too lazy to actually go into the databank after removing any custom code by hand for trying out). |
I have the same problem menu popups stopped working, and seems to have started around the same time with the 6.6 upgrade. |
Thanks yeah that worked. Just makes it a bit complicated as I have to create that menu first... I used a menu for mobile menu so copying over worked. Basically it renders the Atahualpa Menu options obsolete. At least those about hiding pages or posts... From now on menu needs to be managed by wordpress not by Atahulapa options. I used duplicate menu plugin to copy over my mobile menu which is a bit different. Sadly some translations weren't copied so some manual action needed on top. But good it works. Likely we should not close this bug as it's a bit unexpected, so people can read the solution more easily. |
Ok, great to hear. If someone is interested: The relevant code can be found here (if no menu location has been chosen): atahualpa/functions/bfa_header_config.php Lines 31 to 71 in e83c9bf
|
Thank you for the menu fix/work around. I've just applied it to about 4 different sites I look after! All of them now have their drop down menus restored. Many thanks |
Updating to Wordpress 6.6 causes the submenu entries to not open anymore - so yu can only access top level pages from menu1 (and likely other menus).
See solution/workaround: #4 (comment)
The text was updated successfully, but these errors were encountered: