Hey kosmosdigital,

Please post us your login credentials (in the “private data” field), so we can take a look at your backend.

1. Install and activate ” Temporary Login Without Password “.
2. Go to ” Users > Temporary Logins ” on the left-side menu.
3. Click ” Create New “.
4. Add the email address for the account ( you can use (Email address hidden if logged out) ), as well as the ” Role ” making that the highest possible and the expiry about four days
   ( to be sure that we have enough time to debug ).
5. Click ” Submit “.
6. You’ll now have a temporary account. Please provide us here in the private section the URL, so we can login and help you out.

When your issue is fixed, you can always remove the plugin!
If you prefer to not use the plugin, you can manually create an admin user and post the login credentials in the “private data” field.

Best regards,
Nikko

Hi Haissam,

We’re glad to hear that :)
Thanks for using Enfold and have a great day!

Best regards,
Nikko

Hi mednaturalis,

We have already reported this warning to our devs.
Atm, we can only suggest clearing the cache to make sure that it’s not the cached version that’s served on the site and switch to 7.3 (which most people said have fixed the issue) since this issue is still under queue for investigation.

Best regards,
Nikko

Hi Mark Clover,

The code you posted is the standard solution, which is in the documentation: https://kriesi.at/documentation/enfold/icon/#troubleshoot
It is tested to work properly on all CDNs (other solutions are basically just a variation of it) and the only exception is the one coming from Godaddy’s chosen CDN secureservercdn.net.
I haven’t found other workaround as well except for disabling CDN in Godaddy.
You can check further information on CORS in MDN: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS

Best regards,
Nikko

Hi koen_dieren,

Can you temporarily deactivate “Login Authentication Code”? so any moderator can look into the issue.

Best regards,
Nikko

Hi marko7,

You’re welcome :)
We’re glad that we could help.

Best regards,
Nikko

Hi marko7,

I have disabled Responsive Images in Enfold > Performance which removes the warning.
We’ll report this issue to our devs.

Best regards,
Nikko

Hi subrakavi,

Yes, you can do that by first using a child theme: https://kriesi.at/documentation/enfold/child-theme/
All modifications should be added to the child theme (anything in the child theme won’t be lost during a theme update)
Next, register the theme in order for it to receive updates and allow you to update in the Theme Options, further details on this can be found here: https://kriesi.at/documentation/enfold/theme-registration/

Best regards,
Nikko

Hi newmediologo,

Thanks, I have checked on portfolio but it’s using Load More button not pagination.
On the blog page, it seems to work properly on my end, going to the 2nd page and clicking back to the first page works properly as well.
Can you try to use Chrome browser in incognito mode?

Best regards,
Nikko

Hi newmediologo,

Thanks for creating a new thread, we’ll continue the discussion there.

Best regards,
Nikko

Hi Thomas,

Try using CSS word-break, you can refer here: https://www.w3schools.com/cssref/css3_pr_word-break.asp
If it can’t be solved by that, then please give us a link to the page, you can post it in private content.

Best regards,
Nikko

Hi Mark,

Try the shortcut key to justify the text:
– Windows: Ctrl + Alt + J
– Mac: Ctrl + Option + J
Or try the solutions posted here: https://wpintensity.com/justify-text-wordpress/

Best regards,
Nikko

Hi mrsecommerce,

You’re welcome, please try adding this as well:

.html_elegant-blog #top.page-id-440 .post-entry .minor-meta, 
.html_elegant-blog #top.page-id-440 .post-entry .post-title {
    text-transform: lowercase !important;
}

Best regards,
Nikko

Hi subrakavi,

Can you give us both admin and FTP access? so we can inspect on the issue.
Just post the details in private content.

Best regards,
Nikko

Hi Patrick,

Some files may have been corrupted during the update that’s why it wasn’t working properly.
We’re glad that this is now fixed :)
Just let us know if you need further asssistance.

Best regards,
Nikko