avviano

The problem happens when the Combine CSS Files is enabled in the SG Optimized Settings > Frontend > CSS

Sorry about the confusion!

I have started a new thread with Siteground Optimizer here: https://www.ads-software.com/support/topic/siteground-optimizer-causes-underline-url-links/

Cheers

• This reply was modified 1 year, 12 months ago by avviano.

I found the issue. After I updated WordPress and Divi, there seems to have been an incompatibility issue introduced with Siteground Optimizer. After deactivating SG Optimizer, the underlined links went away. I will contact Siteground and let them now about the latest compatibility issue. Cheers Walter

I have the same issue. More than a hundred of my client websites are affected and now show underline on ALL non-button text URL links. This was introduced with the latest WordPress 6.1.1 update.

I cannot imagine that WordPress intentionally forced such layout changes onto websites retrospectively? Changing the CSS on all of theses websites will take me 3-4 or more hours to do. Since I am not the only webdeveloper and designer affected by this, the total hours burned to correct this issue on websites worldwide will go into the thousands!!!!!!

Does WP expect me to change 100+ websites now? The fact that WordPress automatically updated on all my sites, means I was totally caught off-guard. I am being flooded with client emails!!

Please let the WP devs know that this could not possibly have been their intention?!

Cheers,
Walter

• This reply was modified 1 year, 12 months ago by avviano.
• This reply was modified 1 year, 12 months ago by avviano.
• This reply was modified 1 year, 12 months ago by avviano.
• This reply was modified 1 year, 12 months ago by avviano.
• This reply was modified 1 year, 12 months ago by avviano.
• This reply was modified 1 year, 12 months ago by avviano.
• This reply was modified 1 year, 12 months ago by avviano.
• This reply was modified 1 year, 12 months ago by avviano.
• This reply was modified 1 year, 12 months ago by avviano.

I was able to solve the issue. As it turns out, my client send me the “sandbox” API credentials, even though I asked for life credentials. Unfortunately, getting the information at Papyal manually is a bit of a nightmare for non-developers and the majority of my clients say it is very complicated and “geeky”. Not at all easy or intuitive. The fact that sandbox credentials are selected by default doesn’t make it easier.

I don’t like how this new process works at all, and as a webdesigner and developer, I have no desire to go through this nightmare process with clients every time, so I am seriously looking at discouraging clients from using Paypal and will simply ask them to work with Stripe instead. The amount of communication necessary for creating a manual API connection is just absurd.

• This reply was modified 2 years ago by avviano.
• This reply was modified 2 years ago by avviano.
• This reply was modified 2 years ago by avviano.
• This reply was modified 2 years ago by avviano.

Hi Niklas,

Thank you for your quick help.

How can I use the onboard wizard, if I am a webdesigner and relying on a client to provide API?

I have contacted the client, but the information he supplied are the Live keys and seem correct. Why? Because when I enter the information and click “connect” Woo connects to Paypal and everything seems fine. It also says “Connected”. Only when I reload the page or leave the page do I get the error message.

Cheers,
Walter

• This reply was modified 2 years ago by avviano.

I am using Woo PP Payment Plugin Version 1.9.5 (So I assume the SG bug should have long been removed).

I am using Siteground Optimizer for the caching plugin, not sure if this is relevant.

Here is a log entry:

2022-11-04T16:04:59+00:00 DEBUG POST https://api.paypal.com/v1/oauth2/token?grant_type=client_credentials
Response Debug ID: a73884c82f40e
Response: Array
(
[code] => 401
[message] => Unauthorized
)

• This reply was modified 2 years ago by avviano.

I will give it a try, thanks!

I still have this issue!

Thank you very much, that seems to have done the trick!

• This reply was modified 2 years, 4 months ago by avviano.

OK, so I added all available scripts from the dropdown in the “Exclude from JavaScript Combination” field and the Facebook embed still does not work. Only if I deactivate “Combine JavaScript Files” completely does it work again. So there is no way to add an exception.

This is obviously a bug in Siteground Optimizer!

Please send me workaround until you fix it with the next release.

Appreciate your help,
Thanks!

• This reply was modified 2 years, 5 months ago by avviano.

This is the CSS code I am using:

.smart-page-loader {
background: rgba(0, 0, 0, 0.95);
}

These are the duration values I am using.

Duration to show Loader: 1000
Loader to Fade Out: 1000

The behavior is weird, as sometimes it works, sometimes it does not and gets stuck.

• This reply was modified 2 years, 6 months ago by avviano.
• This reply was modified 2 years, 6 months ago by avviano.
• This reply was modified 2 years, 6 months ago by avviano.

Hi Stefano,

All very good news. I will use the manual install smtp for now and I am looking forward to version 1.1.8.

Cheers,
Walter