phoros

Before this thread will be cut out like others with message (last few days):

@phoros, Your comments have been archived for being un-constructive. One thing we ask when commenting on someone’s negative experience is to help them with that experience.

One more time (maybe the last one):
What’s on with You, Guys?…
What has happened to the open community developement?
WHEN did WP become a private playground? :/
With all that censorship and agression?
So dissapointed…

I really hope so.

Thanks & cheers!

The problem is we’ve made in our company dozens of websites based on WP, some of them huge (hundreds of thousands entries, media, etc.) AND we’re on the edge right now: updating and developing / rebuilding those sites will be impossible. And the whole team agrees that IF WP will force Gutenberg we’ll have to switch to a different CMS or create an own one. Tons of wasted time and money.

Nonetheless we’ve started searching for something else just in case.

The funny thing is that the simplest solution lies in front of everyone: just keep Gutenberg as a plugin. Or split WP into 2 distros (like in linux world).

Though I’m afraid that the politics ($$$?) standing behind all this won’t allow for that.

“…why this is necessary…”

No, it’s not. But what I know, right?

Such an answer illustrates perfectly the whole disscusion about this disaster.

Hi.

We have the same issue. I get the idea and the mechanism of header height BUT I want to save a height of the header and at the same time I want to have my menu placed at the top of page, not in the middle of header/row div etc. Additionally, a want submenus directly belowe the main menu (main li elements) NOT after a huge padding/margin.

I’ve started to play around with CSS but results are not so great.

Any help with this?

PS. I’ve found it out.
It’s the line-height value in “.kad-header-style-basic #nav-main ul.sf-menu > li > a”.
I’ve adjusted it in custom css area and everything is fine.

• This reply was modified 6 years, 12 months ago by phoros.
• This reply was modified 6 years, 12 months ago by phoros.

Yes, my WP timezone is set for Warsaw (currently UTC+2h) and all plugins or other scripts work fine. Please correct me if I’m wrong but there must be something in your plugin that works globally and forces changes of time on the entire site. I’d rather suspect the opposite action: time in the plugin could have been wrong due to server or WordPress settings, NOT vice versa.

Of course there also might be a conflict somewhere ‘cos I have a big, heavy modificated site with fifty plugins.

I’ll play around with this later.

Guys,

I had the same issue.

At first I used @maculko’s tip, now the patch privided above.
Works like a charm, thanks a lot.

Please, include this in next updates.
Your plugin is crucial for many of my sites and fixing it manually all the time is a little pain in…..

Nonetheless, thanks for an excellent plugin and support.

Bumping.

I’ve got the same situation with Shoutcast streams: generally it works fine but sometimes (in Chrome often) it just cannot start (‘Can’t locate audio’). Clicking ‘play’ once or twice more makes things happen but sometimes it needs to be clicked several times. Streams are ok and work flawlessly anywhere else.

I like an idea of forcing the player to do few more tries before giving up with ‘Can’t locate audio’. It should do the job and waiting for the stream to start for few more seconds won’t be a problem for anyone.

It would be wonderfull if it works – I’d like to remove other players (outdated and sometimes still on flash) from my projects and stick with this one.

Thanks in advance,
Chris