phil.sklar
Forum Replies Created
-
Forum: Themes and Templates
In reply to: [Life Is Good] Mobile Menu Not WorkingThank you for your help, Daniel! I had deleted the footer.php. When I put the code back at footer.php, the menu worked again on mobile.
Forum: Plugins
In reply to: [Jigoshop] Shop No Longer Configured ProperlyThis has been fixed.
Forum: Plugins
In reply to: [Jigoshop] Shop No Longer Configured ProperlyThat was the issue, and the shop items now up properly at http://www.bobbleheadhall.com/shop (Password BOBBLEHOF14) however the text that was above the shop items no longer shows up. The text is still showing up at Pages > Shop.
Forum: Plugins
In reply to: [Jigoshop] Can "Coupon Code" be changed to different name?The other message that comes up when I go into the “Translation Language File is: “Warning: The actual loaded translation content contains mixed textdomains and is not pure translateable within one textdomain.
It seems, that there is code contained extracted out of other plugins, themes or widgets and used by copy & paste inside some source files.
The affected unknown textdomains are: jigoshop_web_optimization_system ”When I attempt to uncheck the “Web Optimization System” in Jigoshop settings, it always gets automatically re-checked.
Forum: Plugins
In reply to: [Jigoshop] Can "Coupon Code" be changed to different name?I followed this step by step and it should work, but does not. I’m not sure if it is because of the following:
In the localization section, the following warning appears in the Jigoshop section, “Compatibility: Loading Issue: Author is using load_textdomain instead of load_plugin_textdomain function. This may break behavior of WordPress, because some filters and actions won’t be executed anymore. Please contact the Author about that.”
“Compatibility – Hints and Errors
If you get compatibility warnings, than they are often related to a wrong usage of WordPress core functionality by the authors of the affected Themes or Plugins. There are several reason for such reports, but in each of this cases only the original author can solve it:
• Loading of translation files will be performed beside the WordPress standard functionality.
•
Textdomains can not be parsed from source files because of used coding syntax. • Component seems to be translatable but doesn’t use a translation file load call.Reported issues are not a problem of Codestyling Localization, it’s caused by the author of the affected component within it’s code.”