Fatal error on trying to translate Theme “Blog

Thanks for reporting. That is a bug, because the PLUGError class should not be referenced. I will fix this now and rush up a fix.

I’ve fixed this in the Dev version of 2.3.3.

Installing that should avoid the fatal error.

However, you will probably still get a PHP Notice raised because some error occurred parsing the charset header of one of your files. It should show up in your logs.

Are you going to publish stable version?

How could I install development version without deleting current? Will I loose all my current data?

There is problem if I’m trying to install development version about having duplicated directory even if current loco version is disabled

Are you going to publish stable version?

I don’t tend to release a new version for one small fix, and as you’re the only person who’s reported this I’m not in a hurry to release 2.3.3 until it contains something more significant.

How could I install development version without deleting current? Will I loose all my current data?

You won’t lose any translations. PO and MO files are not considered part of the plugin and are never deleted automatically. Just don’t store any of your own files under the plugin’s root folder.

So I should remove current loco translate and instal developement one and would be cool?

Yes, to install the development version you will have to replace the one you have installed.

Hello @timwhitlock , it’s not just @aecorn. I’m also getting the error while trying to build a website for a client of mine.
I’m guessing a lot of others have it but aren’t reporting it. I’m used to googling so I easily found this topic but at first I just thought that the file may have gotten corrupted.

Here’s the exact error. It was generated while trying to edit a translation for a plugin, not a theme. It seems a bit different than what @aecorn got:

“Fatal error: Uncaught Error: Class ‘PLUGError’ not found in /home/absolute/travel/wp-content/plugins/loco-translate/lib/compiled/gettext.php:8 Stack trace: #0 /home/absolute/travel/wp-content/plugins/loco-translate/lib/compiled/gettext.php(8): LocoPoHeaders->getCharset() #1 /home/absolute/travel/wp-content/plugins/loco-translate/lib/compiled/gettext.php(13): LocoPoHeaders::fromMsgstr(‘Project-Id-Vers…’) #2 /home/absolute/travel/wp-content/plugins/loco-translate/src/gettext/Data.php(70): LocoPoParser->parse() #3 /home/absolute/travel/wp-content/plugins/loco-translate/src/gettext/Data.php(38): Loco_gettext_Data::fromSource(‘# SOME DESCRIPT…’) #4 /home/absolute/travel/wp-content/plugins/loco-translate/src/admin/file/EditController.php(96): Loco_gettext_Data::load(Object(Loco_fs_File)) #5 /home/absolute/travel/wp-content/plugins/loco-translate/src/mvc/AdminRouter.php(246): Loco_admin_file_EditController->render() #6 /home/absolute/travel/wp-includes/class-wp-hook.php(287): Loco_mvc_AdminRouter->renderPage(”) #7 /home/abs in /home/absolute/travel/wp-content/plugins/loco-translate/lib/compiled/gettext.php on line 8″

I’m gonna give installing the dev version a shot, I hope it does the trick.

Fair enough. I’ll release this fix as a stable version then.