MattyX

As I wrote in another thread today, and as others say here – hupso.com being down, almost means our sites being down. And I guess it’s a quite legitimate reason to move away from this plugin. I like it otherwise, but I can’t be dependent on some other website to be up for mine to work properly, it’s the main reason I picked Hupso’s buttons to start with – because they are (usually) way faster than other services who force your site to make a dozen nonsense requests upon load.

So, yes – at least make it load totally asynchronously, or to even load without your site at all if it’s down.

I can report that I managed to “hard code” the <?php echo do_shortcode( ‘[hupso]’ ); ?> string into posts and portfolio. So it seems to work like I want it now. In any case, I would still be *very* glad if you could solve this problem. It seems to be very common with share plugins. I only had AddThis working earlier, but it’s incredibly effective at slowing down your site, so I am glad to get rid of it.

webeminence: Nope, a “self hosted” site. What made you think so? I’ve never tried password protecting the login, but it’s a feeling I have, that it wouldn’t work with the app.
In plain text, I am really fed up with having to “tweak” everything everywhere, all the time (just as if I had all the time in the world to spend on these boring matters). Most often just because the Open Source developers who’s mercy I/we are under, “thinks” something about everything. “Nah, we don’t like that. We don’t do security by obscuring things, we like to have you do twenty different tweaks, and install twelve different plugins to make it work properly”. ??

esmi: Yeah, I have no user id1, no admin (or vastly similar) username and +10 letter “secure password”. So there’s not even a chance in a million plain bruteforce would work, perhaps not even billion.

I do have this way to rename login etc. through “Better WP Security”, but haven’t tried it since I read all about these plugins that will conflict with it. So my question is, why don’t future WordPress come with that feature directly in the installation/setup? Instead of all these plugin/.htaccess tweak/external blacklist inclusion stuff. It doesn’t make any sense at all.

Guess the WordPress App wouldn’t wotk with password protecting the login(?). As I often spend like several days without actual access to a real computer, and seldom my own computer, I do need it.

But in any case, I guess you can(‘t?) see the logic here. There would be no need for all these “Why don’t you just” – and all these suggestions, mostly regarding .htaccess. Why not just change the login-URL and/or rename wp-login.php, and problem is solved? Why would that be such a terrible thing to do? There are other platforms where you do, some even require that you do.

In exactly what way is is “beneficial” to keep it the way it is, seriously? If you have a tank, instead of trying to reinforce it with all sorts of non-conventional materials and procedures, why not take it out of sight and thus out of line of fire?

Is there some sort of purpose in itself to keep the current login setup as it is? What would be “worse” about WordPress if the login path wasn’t known? That’s not a sarcastic question, it’s all seriously meant.

To the rest of your answer:

1. They are doing nothing.
2. I have already implemented the suggestions that are convenient for me to use.
3. So it’s less an “obscurity” to be dependent on an external “flexible blacklist that checks all URI requests against a series of carefully constructed HTAccess directives”, than to eliminate the main possibility to even perform these kinds of attacks? Sounds more like modern medicine “Oh he’s sick, give him these pills! To cover the symptoms!” instead of removing what makes someone sick.

Seems to be some sort of OS conflict. Hovering the URL always shows this /# thing. Using an old computer with Win XP right now, where it doesn’t work in either Firefox or Explorer. Then tried a newer one here + my phone, and both of those works. Just so you know.

Having that problem. If I set it through the Addthis settings, there’s no Twitter icon at all. If I set it through the widget itself, there’s this /# link.

I might share with you, that I got to know that “this function is currently disabled”, but it will be re-enabled again in some update.

It took me quite some efforts to squeeze that out of one of their guys. It’s not like I’ll send their office anthrax spores due to this, I was just glad to get to know. I wonder why people just can’t be straight with you, and prevent you from wasting time and energy trying to solve something which can’t be solved?

So, expecting it to be solved in some future update. Not much more to say, I just wished they could be more open about such things instead of ignoring questions or “beating around the bush” with all sorts of weird pseudo-support questions and excuses.

It wasn’t more complicated than the shortcodes at your page, separated by commas like: facebook_like,twitter,tumblr and some more. Nothing changes.

I’ll drop you a mail.

I might add, I just set the parameter to “optional” instead of required, and deleted the whole asterisk input line of code. But out of pure curiosity, this isn’t standard wordpress stuff, is it?