Hi,

Thank you for the update.

One of reasons is, that with extended editor, the Single Post Navigation arrows are NOT shown.

When a slider or any full width element is added in a page, the post navigation will be automatically disabled because it tends to overlap with the full width element. We have to use the following filter in the functions.php file to change that behavior.

function avf_post_nav_settings_mod($settings) {
  $settings['is_fullwidth'] = false;
  $settings['skip_output'] = false;
  return $settings;
}
add_filter('avf_post_nav_settings','avf_post_nav_settings_mod', 999, 1);

When we create a layerslider and set “transparent header”, it works perfect when using the “enhanced editor”.

We actually explained it above. The container in the default template, where the layer slider and the rest of the content of the post are added, is not full width and unlike in the ALB, the layer slider is not added directly below the header before the rest of the content. You have to modify the single.php file, or the includes > loop-index.php file. Unfortunately, this will require changes that are beyond the scope of support.

Best regards,
Ismael

Hi,

Thank you for the update.

The test page no longer exists, so we couldn’t inspect the element. Did you remove it? Please add it again or provide a link to the page containing the element that you want to modify. Or try to use this css code to decrease the height of the titles in the tab section.

#top .av-section-tab-title {
	padding: 0 20px 0 20px;
	display: inline-block;
	text-decoration: none;
}

#top .av-tab-no-image .av-inner-tab-title {
	margin-bottom: 0;
        margin-top: 0;
}

#top .avia-tab-title-padding-default .av-outer-tab-title {
	padding: 0;
}

Best regards,
Ismael

Hi,

Thank you for the update.

The main stylesheet in the wp-content/uploads/dynamic_avia folder is not found. The file should be regenerated whenever you toggle any of the theme options, but it’s not working as it should. Please try to correct the permission settings of files and folders in the server.

// https://wordpress.org/support/article/changing-file-permissions/#example-permission-settings

Best regards,
Ismael

Hi,

Thank you for the update.

The theme doesn’t disable the WP REST API and it’s not using it either, so it’s probably not the issue. The API is already merged in the core, but you can use the following plugin to ensure that the endpoints are enabled.

// https://wordpress.org/plugins/wp-rest-api-controller/

Have you tried resetting the plugin? Create a restore point or a backup of the site first just in case.

Best regards,
Ismael

Hi,

Thank you for the update.

We deactivated the cache plugins and turned off the Performance > File Compression settings temporarily to regenerate the scripts required for the new privacy options. We also set the Default Cookie Behaviour to the first option so that all cookies are accepted on load — user can always opt out manually if they wish. We also enabled the advanced options and set it so that the page auto reloads once the user accepted the cookies. You can always configure the options back when necessary. The map in the locations page now works properly when we check. However, the modal popup window still doesn’t display on page load. We had a hunch that it’s due to the lightbox script, so we created a dummy page and added an image element, and as suspected, the lightbox popup is not functioning properly (see private field). We didn’t find any errors or anything, so it’s possible that there’s a conflict somewhere — with the plugins or a custom script. Can we deactivate the plugins temporarily?

Best regards,
Ismael

Hi,

The changes added to the style.css file or the Quick CSS field will not be included in the merged stylesheet while the Performance > File Compression settings are enabled. You have to toggle it, or turn it off and on again to regenerate the stylesheets and include the recent modifications. That’s how it works. What you can do is keep the settings disabled while you’re working on the site and enable it back once you’re completely done.

Thank you for understanding.

Best regards,
Ismael

Hi,

Thank you for the update.

The indicator for the active anchor is not working properly because you’re not using color sections or grids to divide the content in the page. The anchors names or ID were applied in the link tags and is not recognize by the script that detects for the current menu item. Try to separate the content using color sections or grids and apply the anchor name in the Section ID field.

Best regards,
Ismael

Hi,

Thank you for the info.

We will forward this to the team and have it fix as soon as possible. Please don’t hesitate to open a new thread if you need anything else. Have a nice day.

Best regards,
Ismael

Hi,

Thank you for the clarification.

Unfortunately the snippet above removes all update notifications at once.

Sorry for missing that info. The filter should only unset notifications from the layer slider plugin. Can we access the dashboard and the file server? We would like to test the filter in your installation. Please post the login details in the private field.

Best regards,
Ismael

Hi,

Thank you for the update.

Glad to know that most of the issues are fixed. For the comment form button, please use the following css code to move it downwards away from the privacy checkbox/text.

#commentform .form-submit {
	margin-top: 50px;
}

Best regards,
Ismael

Hi,

Thank you for the update.

You can either trim the content to decrease the height of the container, or adjust the font size of the text inside.

.wpcs_content_main p, .wpcs_content_main li {
	font-size: 10px;
	line-height: 2em;
}

You can also adjust the padding around the content and remove the minimum height from the following css modification.

#wpcs_content_inner_8438 {
	padding-top: 10!important;
	margin: 0px !important;
	border: none !important;
}

div#wpcs_content_inner_8438 {
    display: none;
    max-width: 100%;
    min-height: 0;
    background: #fcfcfc;
    padding: 20px 20px 20px 20px;
    margin: 60px 40px 60px 40px;
    color: #666666;
    border: 1px solid #ffffff;
}

Then adjust the bottom position of the pseudo element.

#wpcs_content_inner_8438::after {
	content: '';
	background: url("/../../wp-content/uploads/2017/12/footer_figures_bg.png");
	width: 190px;
	height: 130px;
	position: absolute;
	bottom: 0;
}

Best regards,
Ismael

Hi,

Thank you for the update.

Have you tried to adjust the height of the color section to make room for the background image? Or try to set the background attachment from “parallax” to “fixed”. The parallax container automatically resizes its container based on the size of the parent color section, so it might not be the best option for the image.

To remove the border of the next section, use this css code.

#after_section_1 {
    border-top: 0;
}

Best regards,
Ismael

Hi,

Sorry for the delay. We created a dummy page and added a few elements, but we weren’t able reproduce the issue (see private field). Is the issue happening on a specific page only? Please provide a direct link to the page so that we can check it.

Best regards,
Ismael

Hi,

? i Have 93GB of Media on the server out of 130GB available disk space.

Thank you for the update.

We can still reproduce the issue whenever we try to access any elements containing an image. It’s possible that the server times out when it tries to query the media library because of the number of entries in the database. The AJAX requests returns the following response.

The site is experiencing technical difficulties.

And this is the error from the log.

[14-Nov-2019 02:14:00 UTC] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 4096 bytes) in /home/wua4p6lmxmxf/public_html/wp-includes/wp-db.php on line 1972

This means that the maximum memory allocated to PHP is only 268MB, not 4GB. This also confirms what we see in the Query Monitor plugin’s PHPinfo tab. Is the site on a shared hosting? If not, then you might be able to adjust the maximum memory limit directly from the php.ini file.

Screenshot of the PHP settings: https://imgur.com/a/cvvVoKU

Best regards,
Ismael

Hey Scott,

Thank you for the inquiry.

You should use the slug/name of the custom post type and it should be lowercase and contain less than 20 characters, so the following line is technically invalid, but it will still work.

 $supported_post_types[] = 'REGIONS';

It should be:

$supported_post_types[] = 'regions';

You might have to edit the custom post type settings in the CPT UI panel.

The block or Gutenberg editor should not be accessible when the advance layout builder is active, so something is not working right in your installation. Please provide the login details in the private field so that we can check it.

Best regards,
Ismael