@calin

I mean exactly what I said.

It seems that you are not keeping track of deprecations.

That is a major problem.

If you are not properly deprecating functions and not following semantic versioning I cannot trust this theme for any of my production sites that I manage.

• This reply was modified 7 years by mgargano.

You still did not answer my questions:

1. In the update from 9.2.2 to 9.5.0 was td_api_header_style::_helper_show_header(); deprecated?
2. Do you keep track of deprecation of functions and methods in your theme?

It’s a rather simple 2 questions. In the update from 9.2.2 to 9.5.0 was td_api_header_style::_helper_show_header(); deprecated?

Do you keep track of deprecation of functions and methods in your theme?

I asked a very specific development related question and your response is generic wordpress information.

Please re-read my question and answer accordingly.

Thanks,
Mat

I turned off the minification, which was *only* CSS. It still does not work. I am using theme files directly from your theme, AFAIK, JS files do not “get corrupted” if you just copy them from a source, they’re literally uncompiled text files.

Please advise!

• This reply was modified 7 years by mgargano.

Thanks

Any update here?

What I mean are. two different sets of code (ie 2 versions) of the SAME plugin are tagged with the same version number

The message is not what I am taking exception with. It’s two plugins with the exact same version 4.4 – AND strict checking via a hash – that violates the principle of versioned software.

@bogdon b. Did you check https://successfulstudent.org — see this screen capture demonstrating the issue: http://recordit.co/h7rY2498zS/gif/notify