bren

while I’m here…
can this not be locally served?
as in place the required files on my server and avoid when Enmask’s server is down

thanks again

Looks like this is going to be a lifesaver but two issues

1 – the server has been down for a while (8th Dec)

2 – you really should avoid using “my_” in a production release.
in wp_enmask_admin.php I had to change the “my_plugin_menu” to “enmask_plugin_menu” as it was clashing with one of “my” plugins ;oP

I’m hoping you get the server issues sorted out.
I was on the understanding this was a cloud service though…

thanks

come on brandonplowe

thanks for the forum support though?
and the solution is?

there are other uber-noobs who would love your help out there

Hi,

I’m looking for this kind of functionality in a plugin too.
(avoiding having to edit htaccess is nice)

As the original OP asked, I’d like that anybody who tries to access /wp-login.php?…
will be forced to
/members-area/
which has my own front end login.

All the other plugins just turn wp-login.php into a pretty url such as /login/
So I guess a simple pretty rename, one entry per line separated by “|” would be nice.
Something like
wp-login.php|user-login/

Other simple but must have things that could be added to this script are
Allow Ajax use of the admin folder even when logged out (that’s where it lives and some plugin writers who use Ajax expect the user to be logged in whereas others allow for those not yet logged in)
and
Setup an easy redirect for sight migration as per these examples

somesite.com/content/lang/en -> somesite.com/content/
somesite.com/content/lang/de/ -> somesite.net/content/
or
somesite.com/content/lang/de/ -> de.somesite.com/content/
even
somesite.com/content/lang/de/ -> theothersite.com/products/

I’ve coded that this manually in htaccess for now but to add this level of tweakability would make this plugin very SEO helpful.
I’m splitting a clients multilingual website into two seperate sites and need to retain search engine ranking.

Oh and fix trailing slash is the other must have

thanks

hey Andy,

thanks for the follow up!
good to hear that you have put some safety checks in.

I’ll be checking back to see how this turns out.
currently I’m hacking my own ‘CRM’ by hooking shopping cart and messaging plugins together
maybe your plugin will have a place when we go for version 3 next time

here’s an idea of what we are looking at

- shop owner can broadcast a message regarding an order
message who: all account holders who are in Canada
limit by: open and unshipped (current) orders
message: CA post office is on strike - your order will be delayed

- customer/shop owner can message one to one on an order
subject: "regarding order # ->
(drop down menu for customers order history)"
body: textarea input

currently rolling my own but would welcome whatever you can add on your CRM base

cheers

argh… hits head against desk

the hack is not working
the shortcode is [my-wp-favorite-posts] but the output stops at <div class=”content”…

ok scrap that… we are in luck

https://nxsn.com/projects/wp-favorite-posts/comment-page-8/#comment-7582
https://pastebin.com/dHq8fXpW

thanks to the person who did the work for us
just be aware that this is a hack to include in your theme functions and not a replacement for the plugin

note that there is an error in the hack at line 50

$output.=wpfp_cookie_warning();

should be

$output.=my_wpfp_cookie_warning();

hopefully the author will release a new API compliant version soon

yes this is because of the following reasons

in wp-favorite-posts.php
function wpfp_list_favorite_posts() is calling the template file in this manner before $content is being checked for shortcodes

if (@file_exists(TEMPLATEPATH.'/wpfp-page-template.php')):
        include(TEMPLATEPATH.'/wpfp-page-template.php');
    else:
        include("wpfp-page-template.php");
    endif;

this means that before the $content is parsed, whatever is happening in the template file is causing the favorite links to be generated ahead of the content rendering thereby circumventing the ability to place the favorites inline as a swap out for the shortcodes

looking at the template file itself, we can see it’s set up to echo it’s contents as opposed to generate a return string

<?php
    echo "<div class='wpfp-span'>";
   ... code truncated for posting here ...
    echo "</div>";
    wpfp_cookie_warning();
?>

I’m sure the author could change this – I’m currently hacking away at the code to try and strip the template into rendering and layout sections so that I can include the rendering inline as opposed to ahead of all content but other things are taking my time

for pointers something along the lines of

<?php

$wpfp_echoStr = '';
$wpfp_echoStr .='<div class="wpfp-span">';
   ... code truncated for posting here ...
$wpfp_echoStr .= "</div>";

//if(wpfp_cookie_warning())...
//generate your warning strings and tag on to output//
//do the same for remove links etc//

$wpfp_echoStr .= '<div class="wpfp-userinteration">';
$wpfp_echoStr .= $wpfp_userinteration;
$wpfp_echoStr .= "</div>";

?>

understand that you will need to work out when and how to call $wpfp_echoStr for inclusion – I’ll report back if I get around to it

great plugin btw!

oh it’s a beta for sure, a public beta (a big difference to that and a private beta)

for a public beta this is pushing the envelope when you are allowed to not only delete user data without confirmation but delete all that user’s data (posts/comments/uploaded non database content such as images etc) without a confirmation before committing and no ability to roll back after pulling the trigger.

and the fact that admin can delete himself and all his settings from the DB is definately not public beta ready.

let’s not forget that this plugin is supposed to be a customer relations (support) plugin.
until they remove the database kill switch it’s not worthy of any realworld (public beta) applications.

don’t get me wrong – looks like its going to be a great plugin – but lets remove the kill switch before we go public – I wouldn’t release a car for public beta if the brakes didn’t work – a private beta in closed circles where people are briefed about the brakes not working is fine.

pitty the fool who doesn’t know who Mr. T is (tounge in cheek) and that a beta without feedback is not a beta ;oP

well I had to do a complete database restore…

pity the fool who uses this plugin for any realworld applications

harsh words yes – but little did I know that deleting user ‘admin’ would delete all his image uploads as well.

I shudder to begin what the paid/extended version of this tool does

please do tell, what else do I have to check up on?

Beta testing has never been so much fun ;o/