jpen365

In case anyone else sees the same issue…

I resolved the issue by adding some JS via a custom plugin. This was in the plugin php file:

function detwit_essb_enqueue_scripts() {
  wp_enqueue_script( 'detwit-js', plugins_url( '/detwit-essb.js', __FILE__ ), $deps = array( 'easy_social_share_buttons-script' ), $ver = false, $in_footer = true );
}
add_action( 'wp_enqueue_scripts', 'detwit_essb_enqueue_scripts' );

So that loads a js file and in the js file was this:

jQuery(document).ready( function () {
  jQuery('a.ess-button--twitter').removeAttr('onclick');
} );

Just linking to the Twitter link is enough to generate the pop-up. The added ‘on-click’ was creating a duplicate window.

• This reply was modified 7 years, 9 months ago by jpen365.

Works great! Thanks!

Hi Rameez. I’ve forwarded the email chain where you mentioned you’d incorporate the fix into a new release of the plugin. If that no longer make sense for you to do, no problem. I’ll just keep using the old version of the plugin.

Thanks for the quick support!

Hi Rameez,

Just a courtesy heads-up that the latest update (7.3) broke the custom fix you had applied on my site. I’ve rolled back to the version you had edited to restore the fix. If you need more info just reply! ??

Jon

I had the same issue and the updated code from the GitHub link above fixed it.

• This reply was modified 8 years ago by jpen365.

Yes, I’m going to upload it a little later today and will send you the link then. Can you provide an email address or contact form where I can provide details? The site is not live yet so I will need to provide you with credentials.

I can confirm that they do offer free support in the support forums. They responded to my question in less than 24 hours which is more than I have any right to expect when using a free product.

Hi Eric. Cron jobs were stuck. All good now.

Headed to leave a 5-star review now. Thanks for the support.

• This reply was modified 8 years, 1 month ago by jpen365.

What you’ve written above is generally correct. However, keep in mind that anyone who views your site can right-click, inspect element, and locate the URL for the image. In addition, if your page is crawlable by search engines, they may locate and index your images. Lastly, anyone can take a screenshot of your webpage and then use that screenshot to share the image.

So, if the image(s) is really something you don’t want to get out in the open, the only thing you can do to really to ensure it’s utmost safety, is to not publish it.

Edit: I just remembered that this is about private pages. Search engines won’t index images on private pages, but if the images are displayed on any non-protected pages/posts, then they may locate and index them.

• This reply was modified 8 years, 3 months ago by jpen365. Reason: Remembered this question was about password protected pages

No one should be able to look through the folders on your web server. That’s called directory browsing and the WordPress core is designed to prevent that. So unless you modify core or use a non-standard file structure (and delete/remove the index.php files you find throughout core), no one should be browsing your files.

The primary way your media files might still end up being exposed is if someone with legitimate access to the content access the media URL directly and shares that URL on social media ,embeds it on their own site, or shares it in some other public form.

This plugin will take care of the attachment pages.

https://www.ads-software.com/plugins/attachment-pages-redirect/

No sure on hiding the image files themselves (going straight to https://example.com/path/to/media/file.jpeg). I’m working on that question for a project though, so if I figure it out I’ll let you know.

Hi, it looks like this plugin will do what you need it to do.

https://www.ads-software.com/plugins/password-protect-wordpress/

Site/Home should be set to https://localhost

Is the http in front of the site / home URL?

The only time I’ve seen what you’re describing (looks like a text mode site) is when I was switching from http to https and hadn’t forced everything over to https yet. Makes me think the http may be missing from your site/home URL in the options table.

It sounds to me like your registrar’s DNS records are still pointing at your old hosting account. As a result, you’re actually still editing your old website.

How long has it been since you updated your domain records to point at your new hosting account?

Try going straight to localhost/wp-login.php

It sounds to me like there’s some sort of issue with your SiteURL and HomeURL.