my site page/post can not visit, showing error - database

I am running a site by Wordpress. My site home page is fine, there have no problem to visit. But other page like, post, category, page do not show. When going to visit, than show this message "
Not Found
The requested URL /terms-condition/ was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request."
Few facts: Few hours ago i got a email that, some one add google web masters tool (a txt file) and a xml file to my site cpnael. I don't know how he/she got the access of my cpanel. May be He/she try to add few content with my site illegally. After that, i remove those and change cpanel password. also i try to increase security by "All In One WP Security" plugin. may be this time something happen with wp table prefix or database. after that i can not visit other page or post. than i removed this plugin from my wp dashboard. But still i can not visit it.
Basically, after setting "All In One WP Security" plugin, i face the problem.
My site url is: http://cleaningservicetips.com/
I can visit home page only not others. How can i get solution?
Thanks in advance.
Al Amin

Go to your permalinks section in WordPress and click update.
Found in WordPress > Settings > Permalinks
This will refresh the permalinks / enable the SEO friendly URL scheme.
Furthermore, you may want to reference this article for more of an in-depth look at WP permalinks. https://codex.wordpress.org/Using_Permalinks

Related

Salesforce digital experience page is sometimes requiring authentication for access even though the guest user has access

I'm not posting any code, but can if anyone believes it's relevant. But the symptoms don't seem to point to the page or the code.
We have configured a Digital Experience. For the experience, we have created a single Visualforce page. The guest profile has been given access to the page and the page's controller. We have assigned that page as the "Active Site Homepage". The site will work as planned, meaning that when going to the base site URL or directly to the page, it will load without authentication. After a given amount of time (which we are not sure how long at this point) of the site not being accessed, when attempting to access the site, it will require authentication.
When that happens we try to troubleshoot. For example, I commented out some of the code on the page that was loading a Visualforce component. Tried loading the page, but it still took me to the login page. So I removed my comments, setting the page back to normal. Suddenly the page starts working and is accessible to everyone, from any location. Even for people who have never logged into the backend org. The page will continue to work for the rest of the day. The next morning we are back to square 1 and the site is requiring authentication.
I thought maybe it was the proxy caching by Salesforce, so I told everyone to stay out of the experience and waited 30 minutes. Since Salesforce says the caching is 10 minutes. But when I went to the page it worked without requiring authentication and I'm pretty sure that tomorrow morning it will start asking for authentication again.
The biggest issue is that we can't seem to troubleshoot. I will make a change to try and see what is happening and sometimes that change will cause the page to work, but then immediately reversing that change doesn't cause the page to break.
Has anyone else experienced this behavior before?
Interesting.
You might have more luck posting in dedicated https://salesforce.stackexchange.com/
Have you tried attaching debug logs? You can find the special {site name} guest user in the lookup and put debugging on for 24h, maybe it'll catch something. Is there any fancy JavaScript on the page that might be causing redirects, lazy loading of some images that might need authentication? Is there a LiveAgent embedded in the community?
Put up as simple version of the page as you can and inspect the generated html. Maybe you're using spyware... sorry, analytics / tracking scripts like Google Tag Manager or Adobe's?
Have you tried browsing with browser's console open (typically F12), maybe you'll catch something weird in Network tab that fails and redirects you to login page. Can you reliably reproduce it in incognito / inprivate / etc mode? Maybe something with cookies?

DotNetNuke - DnnImageHandler.ashx - error 500

Clean Dnn Version : 09.01.01 (129)
When I work with Dnn and have javascript console opened, a lot of times I get error:
/DnnImageHandler.ashx?mode=profilepic&userId=1&h=32&w=32 500 (Internal
Server Error)
At the same time the image in the toolbar profile is missing. Where an how I can see what is working wrong what logs to check? If I go to Manage / Admin Logs and select Log Settings There is a lot of stuf I can enable, but dont know what can be right to see this error and try to find something more.
If I try to open this link in another browser window most of the time everithing is OK and I get generic user image with "?" back.
Also does anyone else see this errors?
Found the same error here:
https://dnntracker.atlassian.net/browse/DNN-9581
It is fixed in dnn 9.2
So I just spent the past hour trying to figure this out, and had to do a lot of cleanup on one of my DNN instances where it was occurring, but once I got all the cleanup done I think it comes down to this.
You're logged in with a Host/SuperUser account correct?
If you login as ANY other user, one of the Users in the Portal, it works correctly?
I ended up having to fix my "profile" page, the site was referencing skins that didn't exist anymore on the profile page, then containers that didn't exist. Once I cleaned all that up, I was able to navigate to the profile page, click on Edit profile, and once I edited the profile, I uploaded a new avatar for the HOST user and was able to get the image to render properly.
I think the issue has something to do with HOST accounts and either referencing an image that isn't part of the current portal, OR HOST accounts and referencing a default image that doesn't exist due to it being a host account, instead of a standard user account.
So how to fix?
Try uploading a profile photo for your account on the current portal and see if that resolves.

Lack of security for force.com sites?

I am exposing a page with a standardcontroller="account" to a force.com site facing the public. This page displays account specific data to the clients. Now when a customer logs in to my website I want him to have access to his account's data and only his account data. Here is the problem; the url for a page with a standardcontroller has a Id field, such as "https//www.myforcesite.force.com/AccountViewPage?Id=a82347dod". If a user changes a few keys on the Id, it is very easy for him to access other people's account page and bypass the login process. How can I prevent that.
I opened a ticket with salesforce but they told me its working as intended. I don't think a vulnerability to a trivial brute force attack should be intended so I want to know if there are any fixes?
Create one StandardController extension and check if the logged user in your website has the permission to view that account.
http://www.salesforce.com/us/developer/docs/pages/Content/apex_pages_standardcontroller.htm
What you are looking for is URL rewriting for force.com site.
For example, let's say that you have a blog site. Without URL rewriting, a blog entry's URL might look like this: http://myblog.force.com/posts?id=003D000000Q0PcN
With URL rewriting, your users can access blog posts by date and
title, say, instead of by record ID. The URL for one of your New
Year's Eve posts might be:
http://myblog.force.com/posts/2009/12/31/auld-lang-syne

Google App Engine - inline/iframe log-in

Is there a way to configure Google App Engine so that the log-in page appears either inline or in an iframe, instead of requiring a link.
I would like it to be as simple as
<iframe src="{{ login_url }}">
<!-- no iframes -->
Log in
</iframe>
However that seems to be an undocumented way to go about logging in users, and I'm not sure if that's the way to go about this.
I'd be grateful for any thoughts
Thank you for reading.
Brian
This is not a good idea. By showing a google login form on your domain how do your users know it is legitimate? By redirecting your users to a page on Google's domain it reduces the amount of confusion.
Also, you might want to review the Terms before doing this. I would not be surprised if Google specifically mentions not doing this somewhere. It's like teaching your users to give up there Google login details whenever prompted.
There have been several posts in the groups discussing this as well; Nick, and many other users, responded to this question with similar comments.
I just tried doing what you suggest here, except that I don't have the hyperlink inside of the iFrame. I want Google's authentication page to appear in the iFrame over my page rather than redirecting to the authentication page and then back to my page. I also append a query string to the login_url, and my main request then returns a simple "Welcome" message rather than my app's main page.
It works beautifully in the sandbox, but it doesn't work when deployed to GAE. The page returned by Google's login_url refuses to be displayed in an iFrame. The console message is "Refused to display document because display forbidden by X-Frame-Options." I've thought about possible workarounds, but Google obviously doesn't want the login page displayed this way. I'm disappointed, because my app uses HttpRequests heavily, so the main page never refreshes otherwise, but I'm still very happy with GAE.

DoubleClick/YieldManager/Ad.com Tracking Pixels - What exactly do they track?

Our marketing team has placed a lot of these tracking pixels on our site. Most of them just make a simple HTTP GET to a URL, usually by using a IMG tag, but some document.write in an iframe/script node as well.
What I would like to know, is what exactly these track. Source IP? What if you are behind a proxy?
These sites cause the visitors browser to go to the site to load the image or javascript. What the site does is store a cookie and/or fingerprint of the visitor. Your site also tells the tracking site something about the visitor -- whether they purchased something or particular aspects of the pages that were vistited. The tracking site than can connect this visit with other visits to your sites, other sites, banner ads or more.
It's called a Web bug.

Resources