Plugin Author
Tim W
(@timwhitlock)
I don’t have any ideas. Please provide a download link to WP Courseware so I can investigate this
Hi tim,
here is the link http://waedow.com/wp-courseware-3.9.zip
thanks for your help!
Plugin Author
Tim W
(@timwhitlock)
The file you mention isn’t skipped once I raise the size limit. More likely you’ve not configured the bundle to use its non-standard layout.
1. The name “wp-courseware” is not the plugin’s text domain. It uses “wp_courseware” with an underscore. It doesn’t declare this fact, so this needs configuring manually in Loco Translate.
2. You don’t need to run the extraction process at all, because the plugin comes with a POT template file already. It’s at languages/default.pot which also needs configuring because the name is non-standard.
3. The plugin also has two typos where the wrong text domain of “wp_coursware” is referenced in the code. These translations will never display due to this error.
Below is a suggested configuration for this plugin. Enter it by clicking the setup tab and then “Import config from XML”.
-
This reply was modified 7 years, 5 months ago by Tim W.
Plugin Author
Tim W
(@timwhitlock)
<?xml version="1.0" encoding="utf-8"?>
<bundle name="WP Courseware">
<domain name="wp_courseware">
<project name="WP Courseware" slug="wp_courseware">
<source>
<directory>.</directory>
<exclude>
<directory>ext</directory>
<directory>language</directory>
<directory>pdf/tcpdf</directory>
</exclude>
</source>
<target>
<directory>language</directory>
</target>
<template locked="true">
<file>language/default.pot</file>
</template>
</project>
</domain>
<exclude>
<directory>css</directory>
<directory>img</directory>
<directory>js</directory>
</exclude>
</bundle>
Plugin Author
Tim W
(@timwhitlock)
Further to point 3. above: there are a lot more of these errors where no text domain is referenced and the translation will never display.
Also note that the supplied default.pot is not in sync with the source code. I count 35 strings from the code that are not in this file.
I suggest you contact the authors about these errors and also ask them to ship a loco.xml file with their next release. Feel free to point them at this thread.