codestyling
Forum Replies Created
-
The bug has been found and gets repaired at upcomming version 1.99.25
The translation service provider would block this as denial of service, because a lot of requests will be created within a short timeframe.
Thatswhy this will not be supported.First of all, your parent theme should be able to load both because it seems to provide both.
If you afterwards derive a child theme, then use the same parent_frontend_domains for your derivative work, thats all.The problem can’t be solved within my plugins, because it has no knowledge about the place, where the translation file will be loaded from.
The path will be generated by filter so the system can’t correctly identify it.
Forthermore the plugin uses the same naming convertion for a method at a class, that also exists as global function. So the scanner can’t locate the textdomain nor the right place of translation file.
In this cases it defaults to plugin slug as base for translation file and normally to one of the folders from plugin to be choosen.This bug has been found and will get repaired with upcomming version 1.99.25 soon.
This extension will show up a lot directories and is not suitable for current version. The work arround is: place the plugin as ordinary plugin into normal plugins with own plugin folder, translate it and use the file from this translation.
I know, that this is not really comfortable but the overhead of enumrate each and any sub folders at mu-plugins an make it selectable for inclusion would require to save somewhere the folder membership to avoid this select process again and again.
Thatswhy this won’t be supported for 1.x versions.Please provide the download link for the theme or send me the zipped theme for investigation purpose. I have no other chance to find out what went wrong in your case.
This is hard to figure out without access to the affected blog. All working the same way independend of plugin or theme. So if one is working, all should work.
It would be necessary to view the behavior at the backend within your installation live to find out the reason for.This script seems to be intended only for frontend pages and not for backend pages. But the Author didn’t care about adding this script only for frontend.
As written at the help tab (upper right corner) or pressing the yellow help button, please contact the Author of “Ajaxy Search Form” and describe the issue. Only those author can repair this.
If this plugin is also intended to work at backend, the Author should contact me after you descibed it.
You have a yellow help button within the warning which expands the help about. Alternatetivly you can also expand the help using the upper right corner help tab an go to “Scripting Guard” section. You will find there (quoted here again):
What can I do, if I get this protection message alert?
If your Installation has this kind of problems, please contact the author of theme or plugin(s) which inject their script code either accidentally or intentionally (click message details). He/she must repair the affected theme/plugin to play nicely with other plugins at WordPress backend and/or restrict its scripts to the 3rd party theme/plugin pages only.
My plugins works with its protection as expected but some other backend page may not. Please contact the affected Authors as written.
The rescan process works, if you enable the low memory mode checkbox at the upper left corner of my plugins page.
Your 84MB with this ammount of installed plugins will not be sufficiant to re-scan WordPress itself without the low memory mode.If version 1.99.22 doesn’t solve your problem, please send me an email about your install. I would need at least access to your backend for investigation of this particular problem. I can’t reproduce it locally.
Please try the new updated 1.99.22 with modified FTP access. You should get it working now.
What is the folder you would access as top folder using the same credentials at FTP Programm?
Still the above named or a folder below lets say ‘lder.me’ ?This is a bug within the message generation only, the function of plugin and also Guard works as expected, because the message will be created using an ajax call.
I’ve scheduled an update very soon, if you want it get working sooner, than you can replace for now following lines (2342 and 2343):<?php _e('Name:',CSP_PO_TEXTDOMAIN);?> <strong><?php echo $ct['Name']; ?></strong> | <?php _e('Author:',CSP_PO_TEXTDOMAIN);?> <strong><?php echo $ct['Author']; ?></strong><br/>with this lines:
<?php _e('Name:',CSP_PO_TEXTDOMAIN);?> <strong><?php echo $ct->name; ?></strong> | <?php _e('Author:',CSP_PO_TEXTDOMAIN);?> <strong><?php echo $ct->author; ?></strong><br/>This fix will be contained at version 1.99.22 comming soon.