We would like the error-log to include the URL (uri) of the original page called by the visitor.
A user visits a web page (URL).
The page is generated by multiple PHP scripts
One of the scripts triggers an error
In the logs, I see the script name that triggered the error.
But I cannot see what URL the visitor visited to trigger this whole thing.
How can we set this up?
Related
I have created page type External URL and assign some permission but page can be open by any users either not log in or non authorized users.
I want to provide some roles to access that URL.
This is by design, DNN does not care about the permissions for external Urls.
The only way to go is adding a "normal" page and add something to that page that redirects to the external page, e.g. some JavaScript. You can use Will Strohl's Content Injection module for that.
I want to disable tracking traffic data for https://www.example.com/something?utm_source=something
How can I achieve this? I only found a way to exclude parameters, but this is not what I need. (https://piwik.org/faq/how-to/faq_81/)
For example when you have a website with a URL of “example.com”, by default Matomo (Piwik) will track all requests for this website, even those requests for Page URLs that do not belong to “example.com”. If you add the JavaScript tracking code on pages of “another-website.com”, these requests will be tracked in your website “example.com” in Matomo.
It is possible to configure your website in Matomo (Piwik) so that only requests to “example.com” will be tracked, and all other requests ignored. Go to Administration > Websites > click “Edit”. Below the “URLs” field for your website, there is a checkbox “Only track visits and actions when the action URL starts with one of the above URLs.”. If you click this checkbox, and click “Save”, Matomo will then only track requests where the domain and the path is an exact match of one of the URLs you specified for this website. This means each valid subdomain has to be specified separately. For example when the known URLs are ‘http://example.com/path’ and ‘http://good.example.com’, tracking requests for ‘http://example.com/otherpath’ and ‘http://bad.example.com’ are ignored.
from: https://matomo.org/faq/how-to/faq_21077/
We are integrating Matomo (formerly Piwik) to monitor our application visits.
We have a page for users to recover their password, the URL looks like :
https://example.com/pwdRecovery?token=ABCDEFGHIJKLMNOPQRST
Could you confirm that it is unsecure to log the URL containing the recovery token with Piwik ?
It is interesting to gets statistics on this page, that is why I do not want to remove my Matomo Tracking code here, how can I remove the confidential part of the URL in my Matomo's stats ?
Matomo (formerly Piwik) handles this for you, you just need to configure the parameters' name you want to exclude.
Login as the Super User, go to Administration > Manage Websites > Global list of Query URL parameters to exclude field.
Documented on their FAQ :
How do I exclude URL query parameters from the URLs tracked, and from Pages reports?
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
I am working on a chrome bookmarking extension with google app engine as the backend. I am the only user now but I thought that if in the future there are other users the url needs to include the user name for the extension to interact with the backend. So I was thinking to change
http://ting-1.appspot.com/useradminpage
to
http://ting-1.appspot.com/user_name/useradminpage
where "user_name" is the gmail user id.
But I looked at twitter url and I see that they have
http://twitter.com/#!/user_name/
What is the purpose of "#!"? Is my scheme good enough in this case?
The # in a URL signifies the 'fragment identifier'. Historically this has been used to identify a part of a document identified by an 'anchor' tag, but recently webapp developers have begun to use it to pass information about the page state to Javascript code running in the page. This is used because it's possible for Javascript code to modify the fragment of the current page without causing the page to reload - meaning it can update as you browse through the webapp, and go right back to where you were when you reload the page.
The fragment is not sent to the server when the browser loads a page, so Twitter's server just sees a request for twitter.com; it's up to the Javascript code in the page to examine the fragment and determine what to do after that.
In your particular case, assuming you're using the App Engine User service to authenticate users, you have a number of options for how to distinguish users in your URLs:
Use their email address. In theory this can change, and users may not want their address in a URL they will share. If the URLs are private, this is more or less a moot point.
Use their user_id. This is opaque and reveals no useful information about the user, so it's safe, but it's also meaningless and hard to remember.
Let users pick a nickname for their URLs, like Facebook and other services do, on a first-in, first-served basis.