1webdesigners

Refresh permalinks resolved issue

ok the php ini manager didn’t have right memory

old php 7.0 had 128mb set

so it was resolved when we reset the php editor for 7.4 to higher memory

resolved

Resolved cpanel and ultimate seo plugin issues

Yui debug info gave me the info to see what was happening

Yui much thanks that’s what I need
I added debug and found issues with an old cpanel plugin and ultimate seo
So we deleted both and then updated to 5.5.1 and bingo it works

So two old plugins were raising flags in 7.4 in older cores and working but 5.5.1 broke them so white screens and critical screens and 500 error

Now that I know what plugins are choking 5.5.1 fatally they are gone

So beware anyone of cpanel plugin and ultimate seo plugin

They will crash 5.5.1

Thanks everyone

Here’s my server running lots of plugins updated, and an old core with 7.4 php

https://1lawyer.org/

It works

If I update to 5.5.1 core

It will be like the rest of sites with updated core broken

No woo on this site, but this is what I’m dealing with

So it’s not the plugins, it’s not the theme, it’s the 5.5.1 core that is breaking stuff IF I upgrade any site to 5.5.1 core

Core is 5.4.2

This site has most of the stuff we use

The same theme
Slider 3
SEO
Contact Form
Few other plugins

So everything works under 7.4 php

As long is core is not 5.5.1

So it’s the core

• This reply was modified 4 years, 5 months ago by 1webdesigners.
• This reply was modified 4 years, 5 months ago by 1webdesigners.

This is the issue, sites with old core 5.4 whatever WORK on 7.4, all the plugins of the site work, as soon as we update the core, IT CRASHES the plugins

So while everyone is saying it’s plugins, it’s not, the plugins work on 7.4 IF we have the old core.

So what is crashing the sites?

It’s not plugins, it’s the core, so if we want to run 5.51 core with plugins that work on 7.4 with older core versions, we now have to remove almost every plugin running 7.4 php with 5.51 core.

It’s core issue on my server.

Not plugins

If it was theme or plugin they wouldn’t work with older core versions, it’s the latest core that is wreaking havoc, now it’s probably something on the server that isn’t enabled that core 5.51 needs

I hope this makes sense to someone that understands, plugins are fine and so is theme on 7.4, it’s only updating the core to 5.51 that is crashing everything

We ruled out themes by testing issue with 2020
That was first thing we thought, since that is the one common thing on all sites, we use only one theme.

My host says the php_mysqlcld (?) is on all versions of php installed from 7.2 to 7.4

So it might be the nd_mysqli file and the associated one since goes back to V 5.0 php and this server only started with 5.6

I looked at error log on a couple of sites we were testing by going from 7.0 to 7.4 and saw nothing in error log within cpanel, it shows a couple of error logs and the only error we really saw was bad logins from hackers.

So it’s core related, things work on 7.4 until we update core on any site to 5.51 and then bingo, it breaks everything, and then only works removing all plugins then turning on woo, and it works and as soon as any plugin is added to core and woo in Centos it crashes.

It’s server time which usually pulls utc

So it’s probably 9 hours ahead of you utc

Each line is a calculation

So hours rate totals that line

Granted if it was total hours x one rate, it would need to be designed different.

I’ve been doing labor parts for invoicing for almost 40 years

We used two hour rates lots of clients

Example auto body has body rate mechanic rates

Just like we have multiple rates our industry

Web design
Custom programming
SEO
PPC
Social media

So for us, it is great, 10 hours web design this rate
5 hours SEO this rate

So it’s actually well designed to handle sticky issue of different rate hours.

But that’s how it works

SI creates a unique field called BUSINESS

Only new users with info in Business field will trigger user being in drop down menu

I just saw the warning no support

So I will visit the support site

Thanks

deactivated all plugins
ran this with just woo
same problem

then I reset permalinks to default

it worked

then I redid permalinks again to post name

it worked

so I don’t know what was wrong but playing with permalinks fixed it

I turned back on plugins we use

it’s still working

so that was my fix, I can’t believe they are ignoring this forum

it’s a nice little script

ok
Thanks

The error page is going to nonsense about streaming
https://support.google.com/youtube/answer/3037019?visit_id=1-636244947053732574-220731114&p=player_error1&rd=1

We tried the pages with all types of situations, reboot machine 1 browser 1 window and still the video is dead

When you look at how long the embed key is, that’s the problem IMO

I’ve never seen keys that long

Like I said if you can just put the url of the video inside simple EMBED tags, there’s no need to even use a key generator, I guess google still wants you to use an api key to grep lots of data, but the video post can just dump the url of the video inside embed and bingo it will work fine

Oh, the youtube title is creating title tags at least, in both WP and our SEO plugin, only thing it doesn’t have is description and keywords which we like to use

I’ll look at the meta tag section to see if putting something for description in it will help add to description title plus site name plus keyword, as it is the titles are not generating video title with site name to make them unique

• This reply was modified 8 years ago by 1webdesigners.

This is the list we use

PLzh_j2zIXaxjvalntNbX4uct4Wm0ex7qx

I looked at the code of the new posts and it has a youtube-player class tag, we stopped using youtube class tags years ago, we just put a videos youtube url inside [embed]url[/embed] in wp now and it plays fine.

Also the call string is huge that your program is generating

Example

<iframe class=”youtube-player” type=”text/html” width=”100%” height=”400″ src=”//www.youtube.com/embed/UEx6aF9qMnpJWGF4anZhbG50TmJYNHVjdDRXbTBleDdxeC41MzY4MzcwOUFFRUU3QzEx” allowfullscreen frameborder=”0″>
</iframe>

So if you just grep the videos normal url and wrap it inside [embed]

Then the videos will work

then if you could figure out how to drop the title of the video into header tags such as <title> and duplicate the title with a user data string like site name for <description> you would have a commercially viable product that aggregators would drool over.

LOL

That’s the main issue all aggregation plugin’s have, they don’t do the simple SEO work of creating header tags and the video titles are natuarl for <header> and the rule for description is do not just duplicate header so adding a user data string to header fixes the no dupe tag issue of SEO, as far as keywords, SE’s don’t need them now but headers and descriptions are a big part of SEO still.

Anyway, that’s he bug we have, first play list we created inside a brand account and the api key generated a long embed string that chokes, instead of a normal embed address.