Hi,
Glad that you have this sorted out now, if you have any further questions please open a new thread and we will be happy to help.

Best regards,
Mike

Hi,
When I check your homepage there is no content, so I checked the page linked below, and I see for mobile the header shows and when I scroll the header scrolls away.
As I read your posts above I believe that you want a transparent mobile header and hide the burger menu.
For this, please add this css to your Quick CSS field:

@media only screen and (max-width: 767px) { 
  .responsive #top #main {margin-top: -80px!important;}
  #top #wrap_all .av_header_transparency {background-color: transparent!important;}
  div#header_main > .container {display: block !important;}
  #avia-menu-0 { display: none;}
  }

After you apply the CSS please clear your browser cache and reload the page to check.

Best regards,
Mike

Hi,
Thanks for your feedback, when I check in your burger menu the search icon has a dark color so it is hard to see, try this css in your Quick CSS field:

.html_av-overlay-side.av-burger-overlay-active #top #wrap_all #header .menu-item-search-dropdown a {
    color: #fff;
}

This should make it white, feel free to adjust to suit.
After you apply the CSS please clear your browser cache and reload the page to check.

Best regards,
Mike

Hey lucybb2,
Thank you for your patience and the login, I see your CPT “Journal” do not have a ALB builder field, I believe that this is because your CPT is not enabled in the theme. Typicality you would enable Enfold Theme Options > Layout Builder > Show advanced options

Then add your CPT to Activate Your Custom Post Types For ALB

and now the ALB button shows in your CPT:

and now you can add elements to the page:

I did the steps above for you, please check.

Best regards,
Mike

Hi,
To have the Hover Background #D4AF37 with black text and a radius of 10px use this css instead:

div div .av-dark-form .button {
    background: #000;
    color: #ffffff !important;
    border-radius: 10px;
}

div div .av-dark-form .button:hover {c
    background: #D4AF37 !important;
    color: #000 !important;
}

After you apply the css please clear your browser cache and reload the page to check.

Best regards,
Mike

Hi,
Glad that we could help, if you have any further questions please open a new thread and we will be happy to help.

Best regards,
Mike

Hi,
Glad that Rikard could help, if you have any further questions please open a new thread and we will be happy to help.

Best regards,
Mike

Hi,
When I test, a Contributor can not view widgets. I don’t believe a Contributor should have this ability. Perhaps you are using a custom user profile plugin to allow this?

Best regards,
Mike

Hey dp-beheer,
Thanks for your question, the correct pagination url is /?avia-element-paging=2 this can not be changed to /page-2 as it would be a conflict with the WordPress pagination. I don’t see anything on the Pagination Best Practices page to point to a diffidence between /?avia-element-paging=2 and /page-2. Nonetheless, if you would like to request this pagination change, the Dev Team has opened a new Github Feature Request for users to place requests and follow them as the Dev Team reviews them.

Best regards,
Mike

Hi,
Please see the Custom Elements Advanced Options documentation.
Günter writes: Add the add_theme_support and then select 2nd option in “Custom Elements for subitems”.

Best regards,
Mike

Hey Bruno,
This is from a background image on the section below the title bar, see the image url below, the best solution is to remove the image.

Best regards,
Mike

Hi,
It sounds like you have this sorted out now, please let us know if we should close this thread.

Best regards,
Mike

Hi,
Glad that this helped, the css should work even though your site is in private, but we will need to see it to examine why it is not working for you.
Please include a admin login in the private content area and a link to the page with the issue so we can be of more assistance.

Best regards,
Mike

Hi,
Glad that Guenni007 could help, thanks Guenni007, if you have any further questions please open a new thread and we will be happy to help.

Best regards,
Mike

Hey Marcel,
Thank you for your patience, the avia element pagination should be /?avia-element-paging=2 not /page/2/ otherwise it will be a conflict with WordPress.
This is why you are getting a 404 error for /page/2/ thus the /?avia_forced_reroute=1
The reason /optiker-leipzig-angebote-rabatte/page/2/ works is becuse it is the native WordPress catagory URL and not the element.
I’m not sure how you achive the /page/2/ in the pagination of the element, but this is not correct, please see our demo here, often users try to change the url from /?avia-element-paging=2 to /page/2/, but will not work.

Best regards,
Mike