Support » Plugin: Cyr-To-Lat » class Cyr_To_Lat\Settings not found

  • Resolved Marian Kadanka

    (@mariankadanka)


    I’m using custom code, hooked on ctl_table hook, to modify translation table. Yet another breakage caused by your code in recent year.

    You’ve changed Cyr_To_Lat_Settings to Cyr_To_Lat\Settings last year, and to Cyr_To_Lat\Settings\Settings now, without any attempt to be backwards compatible!! Causing PHP fatal errors due to reckless renaming!

    readme.txt is not updated to reflect these changes!

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author kaggdesign

    (@kaggdesign)

    We do not promise to make our internal code backwards compatible. Please read the description of the Semantic Versioning (Semver). There is written that the first number is the major version. The major version is increased when the software receives incompatible API changes.

    We only promise that plugin filters and actions (API) are still the same within major versions. In our case, with version 5.x.x, even no such changes present, and filters are still the same.

    What I may suggest – use filters. I doubt that your case requires intervention to the plugin code. Please let us know what you are trying to do and I will try to propose the solution.

    Thread Starter Marian Kadanka

    (@mariankadanka)

    Haha, did your at least read what I have written?

    It’s not your internal code, read your own readme.txt (or FAQ), “How can I redefine non-standard locale?” paragraph – I’m using exactly this piece of your own outdated code, using your own hook, based on your own official FAQ, which broke second time in the past year! So what are you talking about, sir?

    Plugin Author kaggdesign

    (@kaggdesign)

    We will fix readme.txt in the next version of the plugin.

    Plugin Author kaggdesign

    (@kaggdesign)

    We have introduced a new filter and described it in the readme.txt, in the “How can I redefine non-standard locale?” section.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.