Mark
Forum Replies Created
-
Forum: Plugins
In reply to: SIMPLEMAP plugin – custom markersAdd the code below to the functions.php file for your theme. Then put an image called marker.png into the images subdirectory of your theme. That’s it.
add_action( 'wp_head', 'custom_markers' ); function custom_markers() { ?> <script> function simplemapCustomMarkers() { var blueIcon = new GIcon(G_DEFAULT_ICON); blueIcon.image = "<?php echo get_bloginfo('stylesheet_directory') ?>/images/marker.png"; return { icon: blueIcon }; } </script> <?php }Forum: Plugins
In reply to: [Login Lock] 3.3 Fatal Error with Login LockIt’s appropriate to post here in terms of WP, but if you’re expecting support and a bug fix to the plugin you need to follow the instructions in the readme ( you said you did ). Many, many, devs have their own support forums and other support methods and do not have time to check this forum, particularly when a plugin is given away freely and generates no revenue to cover the time involved with cruising the forum…
Forum: Plugins
In reply to: [Login Lock] [Plugin: Login Lock] Fatal ErrorThe only safe, OFFICIAL, download page for Login Lock is at ww.wp.xz.cn.
http://ww.wp.xz.cn/extend/plugins/login-lock
@daniel – you can stop posting promotional links to your forked code now.
Thanks.
Forum: Plugins
In reply to: [Login Lock] 3.3 Fatal Error with Login LockProlly should get in the habit of inspecting the readme for plugins since invariably that’s the ONLY way we devs have of communicating info to users of our plugins…
At the same time – only few plugin devs have time to cruise the forums here. We’re usually busy writing code and paying bills – since these plugins are free we gotta make some money elsewhere.
Your dashboard should eventually update to indicate a new version is available.
Forum: Plugins
In reply to: [Login Lock] [Plugin: Login Lock] Fatal ErrorsCheck the readme file for how to report bugs and problems.
Forum: Plugins
In reply to: [Login Lock] [Plugin: Login Lock] Mask login failure info to visitors?Hey Daniel, kindly quit posting links to your fork in threads related to my plugin now that I fixed it. Thanks.
Forum: Plugins
In reply to: [Login Lock] 3.3 Fatal Error with Login Lock@marjwyatt : You shouldn’t be surprise. The readme file clearly tells people how to report bugs and get support – which incidentally doesn’t include posting to this forum.
Forum: Plugins
In reply to: [Login Lock] 3.3 Fatal Error with Login LockI just pushed v2.2.4 into the plugins repository. Hopefully I got the fix for the ” is_rtl() is not a function ” problem resolved. I’m not sure though since I don’t have such a system to test with.
I just pushed v2.2.4 into the plugins repository. Hopefully I got the fix for the ” is_rtl() is not a function ” problem resolved. I’m not sure though since I don’t have such a system to test with.
Other fixes and changes were implemented, some courtesy of Daniel Convissor.
Some will some won’t. For example, your idea of removing what you term “self promotion” from the login form will stay in the plugin. Reason being, a lot of people actually contact me via that link when they have problems that they think is related to the plugin. In most cases it’s not related, and in all cases they get free consulting from me as to what the problem actually is and how to remedy.
That’s one instance. I haven’t reviewed the other changes yet. I’ll try to do that today if time permits – me being a family man will bills to pay.
As a follow up, it was evolutionaryit who contacted me. Thanks.
Fix is forthcoming.
If you guys bother to check the FAQ section in README you’d find really really really clear info on how to report bugs – which incidentally doesn’t includes using this forum. Just sayin’…
Fortunately a forum reader went to my site and sent me a note via the contact form – the preferred way to deal with issues with my software.
It’s probably good practice to check the README for all plugins.
That said, I’ll look into fixing this issue.
Forum: Plugins
In reply to: WP E-commerce Members Only moduleNot possible using the stock plugin.
WP e-Commerce uses third-party payment gateways, so the WPEC cart never sees the card number.
This is the SAFEST way to run a cart. When you store other people’s card number you suddenly become liable for what happens to the card numbers – AND – you must comply with the credit card industry PCI Payment Standards, which are tough!
The WP core files are all the files that come in the zip download:
Unzip that to your local system, then FTP all the files and dirs up to your live site.
So here’s the solution:
Reinstall all WP core files.
So here’s the reason it happens:
Automatic upgrade automatically fails when it can’t automatically do everything it needs to automatically do. In some cases we wind up with half a copy of WP 3.1.4 files and half a copy of WP 3.2 files. Not good.
Anyway. Problem discovered and solved 🙂