andreiglingeanu

Hi @mendozal,

Thanks for reaching out. I’m sorry this problem happened for you.

I have a strong suspicion that this problem happened because of a broken update of the Blocksy theme. Sometimes, during WordPress updates some files can be getting lost and not end up in the final build.

And, it looks like in your specific case, the “wp-content/themes/blocksy/inc/css/fundamentals.php” file is missing —?this is the file that contains the “blocksy_default_responsive_value()” function.

Can you please try to re-install the Blocksy theme from scratch (ideally by uploading the ZIP through FTP)?

I believe this should fix this situation. But, if it doesn’t, please reach out with results and we will keep looking for a solution.

Looking forward for your reply.

@danipperez definitely not something expected. Which error do you get? Maybe while changing the files by FTP you also overridden the permissions? And because of that WordPress no longer can run the update.

This turned out to be a server issue, specifically how it handles the “media_handle_sideload()” function. Needs further investigation from the hosting side.

@technicaljayendra please ignore the options about Ads & Groups! These are automatically detected custom post types, these custom post types should be skipped, really.

Can you please let me know which plugins you have that could have been declared these custom post types? I’ll make sure to get rid of these options.

The small text can easily be adjusted by changing the font size from the corresponding typography options.

Also, can you please let us know which items correspond to this error “Clickable elements too close together”?

@nyodulf thanks for the feedback, it’s appreciated!

Just so we can have a productive conversation, which edited sections seemed obtrusive and inappropriate? Are you talking about the customizer or it is only about the user profile which you mentioned?

The goal with the customizations was to be as close to Core’s design guidelines as possible but also accommodate our options, at the same time. We understand how important it is to stay consistent with Core’s design language and keep the user flows the same.

We’d be happy to make adjustments to our styles but we first need to understand which parts are the most problematic.

Looking forward to your reply!

Best,
Andrei.

That makes sense. Thank you.

Anyway, the code snippet is useful for the ones that want to get this fixed, even in the free version of Polylang.

Confirming this issue, can reproduce it too.

And yes, the issue goes away when the debugging is off.