My WordPress site is not accessible for external users. The only page there is should be published. It's not set to private or anything else. I checked every setting I can think of.
I'm working most of the time in Google Chrome, therefore, my Wordpress account is still logged in and I'm able to see the webpage. But when I go on safari and type in the URL. It will take me to the wp-admin login page. This is strange since the page should be published.
I'm not using an FTP server.
Any ideas?
Related
I have a WordPress site that has a lot to do with Membership. I embedded the site in another site I own, but whenever a user logs in through the iframe or embed, it refuses to login or show user details. I really need the website to work in iframes and allow logins cause I plan to sync it with an app and another website. How do I resolve this please.
I'm a new WordPress designer. My site runs Tesseract Theme and is built with Beaver Builder.
PROBLEM: When I post my website (https://louiseclark.tech) on Facebook it removed my site after a couple minutes. Now when I try to post my site it gives me this message--> It looks like a link you're sharing might be unsafe. If you can, please remove this link: louiseclark.tech Note: The unsafe link might be on the page you’re linking to.
What I've done to try and resolve:
When I ran my site through the Facebook debugger I got this message:
The 'fb:app_id' property should be explicitly provided, Specify the app ID so that stories shared to Facebook will be properly attributed to the app. Alternatively, app_id can be set in url when open the share dialog.
I created an app id following this instructional video: https://www.youtube.com/watch?v=V97h03H21y0
I pasted my app id into my Yoast SEO plugin under the Facebook category.
Check my Google Webmaster Tools Sitemap...all is verified and sitemap set.
SSL certificate is set - checked with my hosting company SiteGround. When I asked them about this problem they didn't really feel that the security issues where from their side.
I've reported this problem to the black hole that is Facebook support.
Thank you for any insight.
In case anyone sees this thread, I found the solution.
When I moved my WordPress sites to managed WordPress hosting I also migrated my websites to https with the SSL certificates. While the pages were migrated and displaying the https just fine, the images still held their old url (http).
I did two things:
I installed SSL Content Fixer plugin. This worked for some images but not others.
I installed Better Search Replace plugin. I had found the specific insecure images using Firefox. From my page in Firefox, I went to:
Tools -> Page Info -> Media This showed me every image/js/css call on this page. Finding these images allowed me to use the plugin to make the changes.
It worked. I'm quite sure knowing how to code my site would be much better in this situation. But I'm a newbie and this is what I could come up with.
What I learned: It's a flag when you have a secure site that embeds non secure objects/images.
I have a SilverStripe blog website set up on my domain and hosting. However, for now when people visit my URL I want them to come to a landing coming soon page as I want to do some marketing and create a small database of users prior to launch.
How can I do this without having to remove the SilverStripe Project from the hosting?
I thought it may be as simple as adding a new index.php page. However, even with this it comes straight into my blog website rather than the landing page I made.
One way to do this is by using this SilverStripe Maintenance Mode Module.
This module allows an administrator to put site in offline mode with 503 status to display a 'Coming Soon', 'Under Construction' or 'Down for Maintenance' Page to regular visitors, whilst allowing a logged in admin user to browse and make changes to the site.
You can customise the maintenance page to say whatever you like.
I'm new to trying Wordpress development. I'm using wordpress.com directly to develop my first site. I'd rather not have to use FTP or anything more than just their website to continue this development.
I'd like the page to not be online until I'm ready for it to go public. How do I "turn off" the page - in other words, can I disable it so that only I can see it? Thanks!
You can use coming soon plugin to your site that prevents user to view pages of your site.
But when you login to your admin, you can see all those pages. So that you can continue your development.
There are numerous plugins which adds coming soon or landing page to non logged in user and shows page content to administrator.
You can try this plugin: Ultimate Coming Soon Page
If you want to set page not publicly you can set particular Page as a Draft from the sidebar there is a button Save Draft
i suggest you develop on your local PC. it will give you full control and once done you can move this site to your online site.
this may help you.
Installing WordPress Locally
I recently upgraded to WPMU 2.8.6 and ever since, my users can't log in on their individual blogs, but they can log in from the main page.
My site is at blogs.mtwp.net (we're a school district).
So if a user goes to blogs.mtwp.net/BLOGNAME/wp-login.php, their password is rejected. If they go to blogs.mtwp.net/wp-login.php, they can log in and get to the dashboard from there.
But it's not all users. Site admins can get in just fine.
We're using wpDirAuth 1.4 if that makes a difference.
Honestly, I'm stumped. Any help would be very much appreciated. Thanks!
you would seem to have enabled the WPdirauth plugin at the top level blog but not on others. Only your top level blog will have the necessary information to connect to your directory.
Site admins are not typically part of your internal directory - they're a Wordpress user which means they can still log-in ok without needing to connect to Active Directory or whatever you're using.
Enable WPdirauth on all blogs that you need users to login to.
Try reviewing your wp-config file. You should see something like this:
define('SUBDOMAIN_INSTALL', true);
Depending on how you've configured Wordpress, this must be enabled to log in to the dashboard of secondary sites.