Hi,

Using special HTML characters is a known problem that cannot be solved without the risk of breaking other things.

As this is not often needed we created a plugin where you replace the special characters:

https://github.com/KriesiMedia/enfold-library/blob/master/integration%20plugins/Enfold/Special%20Character%20Translation/avia-special-characters_1_0_0.zip

The translation list is here:

https://github.com/KriesiMedia/enfold-library/blob/master/integration%20plugins/Enfold/Special%20Character%20Translation/translation.txt

If you need more characters you can use the filter avia_special_characters_translations.

Best regards,
Günter

• This reply was modified 5 years, 8 months ago by Günter.

Hi,

If this can be fixed it must me done in WordPress core. So contacting WP is certainly a good idea.

Best regards,
Günter

Hi!

Thank you for reporting this.

We will provide a fix in core.

Meanwhile please add to Enfold -> General Styling -> QuickCSS:

.avia-image-container.av-hover-grow:hover img {
    -webkit-transform: scale(1.1);
    transform: scale(1.1);
}

.avia-image-overlay-wrap {
    overflow: hidden;
}

Regards,
Günter

Hi,

Sorry for the late reply.

Sounds like the file is corrupted. Download a new zip file from themeforest, delete all enfold folder and try a new upload with ftp.

If you need help, please give us WP admin and FTP credentials and we can do it for you.
There will be 4.5.5 released shortly.

Best regards,
Günter

Hi,

I updated a few lines of code in enfold\framework\php\class-framework-widgets.php to get more information: Instagram returns 429 – Too Many Requests.
Changing the username to an invalid one also returns the same.

I can access your account from my dev environment.

Check: https://stackoverflow.com/questions/33477861/how-to-avoid-instagram-error-429-the-maximum-number-of-requests-per-hour-has-bee

What you can try is to create a new account and check if the same problem occurs. Seems that your IP is blocked by instagram.

Best regards,
Günter

Hi,

As far as I’ve checked there is no (easy) solution for this problem:

WP uses:

/page/xx resp. &paged=xx

Digging into the logic of WP:

Archive pages

These use the parameters and query the requested page. When using an out of range page number this returns no results and WP redirects to 404

Single pages, posts, ….

Using a valid page/post/…. always returns a result.
The page parameters are ignored by the WP query (as they make no sense in case of a single page) and can be used by the content, e.g. ALB blog post element.
The page content is displayed – elements of the content can return results or not depending on page parameter. But this is done during rendering the content (and after output of headers).
A 404 would only be possible with rerouting and must be handled from the element.

If you check https://kriesi.at/themes/enfold-2017/blog/page/5/ you get an empty content for the blog post element – The page exists, but part of the page has an empty content.

I keep the issue open in our dev repo.

——————
Update:

After talking to Kriesi:

As this behaviour is the standard behaviour of WP we do not intend to change this in core.

Best regards,
Günter

• This reply was modified 5 years, 8 months ago by Günter.

Hi,

Welcome. Glad we could help you.

Best regards,
Günter

Hi,

This behaviour you describe above also occurs when you use a standard WP Theme like 2019.

– Activate the theme
– Create a new page with only plain text inside (e.g. a-custom-normal-page)
– Open the page (http://localhost/wp_demos/a-custom-normal-page)
– Extend the URL with /page/52 (http://localhost/wp_demos/a-custom-normal-page/page/52/)
– Open this link and you recieve 200 and the pagecontent
– Use http://localhost/wp_demos/a-custom-normal-page/pages/52/
– Open this link and you recieve 404 and the 404 page

Using Enfold behaves similar, when you select a custom 404 you get the custom 404 page instead of default 404.

I agree that this behaviour is strange – I will open an issue for that in our dev repo but I’m not sure if this is something we can solve. It seems that WP does not recognise this as 404 or it’s a bug in the routing of WP.

Best regards,
Günter

Hi,

I found a solution adding support for the standard WC filters for product grid, product slider and product list. You will find an option for each element to activate the filter support. But that would mean to update 6 files.

Kriesi is planning a release (4.5.5) in the next days. Can you wait?

Best regards,
Günter

• This reply was modified 5 years, 8 months ago by Günter.

Hi,

Great we could help you. Fix is part of a pull request in our dev repo and will become part of the core.
Enjoy the theme.

Feel free to open a new topic if you need further assistance.

Best regards,
Günter

Hi,

@boehmmedia

Strange – I checked it with 4.5.3 and it works for me. If you are using an older version of Enfold there had been some changes to the Envato API that might cause the problem.

Can you open a new topic and provide us WP admin credentials so we can check the backend?

Best regards,
Günter

Hi!

I tested it with Enfold 4.5.4 and WP 5.1 and it works on my install.

Regards,
Günter

Hey webworm72,

Thank you for using Enfold.

Could you create a WP admin account for us and a link to the site so we can check in reality and backend? There are so many settings that it is nearly impossible to help without seeing them.

Best regards,
Günter

Hi,

Thanks for reporting this.

Can you try to upgrade to the latest version 4.5.4 and check? There had been a heavy change in the implementation how 404 and maintenance mode are handled.

I also added this to our dev issues to check.

Best regards,
Günter

Hi,

Thank you for using Enfold – and sorry for this.
I’ve seen this topic for the first time today.
I opened an issue in our dev repo and will have a look into it asap.
Please keep the login credentials valid so I can have a look in the backend.

I will come back to you.

Thank you for your patience.

Best regards,
Günter