I'm experiencing a very strange problem. The user sees in the browser another content of a subpage than the page editor has defined. I have no idea where TYPO3 gets the wrong content. If I preview the page from the editor it is everything correct. But from the view of a normal visitor of the page I see the wrong things.
Following TypoScript:
config {
// Administrator settings
admPanel = {$config.adminPanel}
If there are some hidden or user restricted elements, they will be shown as long as you're logged in the backend as well (Maybe check the admin panel preferences, take a look here: http://typo3.org/1215.0.html )
Related
I have a Home page with links to Offer page and Contact page, which are different .html files, and a Home page, which is current file.
First two have attributes: target="blank", and rel="noopener noreferrer".
When i click on one of those links, it correctly opens new page in a new tab.
But when i come back to Home page using Home link and then i try to open one of the two first links, the attribute target="blank" doesn't work anymore and I'm getting redirected to chosen page, instead of opening it in a new tab.
Can anyone explain what is happening? Can i change this behavior?
In my local environment of a particular site, when i click on a particular link ,it redirects to the same page but in the url it shows that the page has been visited.Again when i click on the link, it will direct me to that page. Any reason as to why this happens and what could be the possible solution.
For example: My sites name is abc.com. It has pages like help, contact etc. When i am on my homepage and click on help it redirects me back to my home page but in my browser the URL is shown as abc.com/help.
When i click on help again , it redirects me to the help page(URL in browser is abc/help/Help) on the second click.
This can happen if the cache or system index has been corrupted. The best solution is to typically stop & start the application and see if it comes back.
If it is still an issue and you are on an older version of DNN, make sure that the PortalAlias table doesn't have a trailing / on your portal alias.
If this isn't the case, it is possible that a custom URL impacted this, but doubtful.
I am using Rails 2.3.5
What I am trying to do is, by using iframe, I am embedding another website's log in screen into my own website.
Problem is starting when I try to "log in" the website inside the iframe. It is working perfectly fine in Chrome and Mozilla bu not in IE (what a surprise).
To be clear: I am able to see the website inside the iframe only thing that I couldn't do is logging in.
Possible problem: I made an extensive research and I learned because the IE doesn't remember my session (doesn't set cookies) I am not able to log in the site inside the iframe.
p.s : using divs probably won't work for me because if I use div and then log in (hit submit button of that website) then I will end up the website inside my div (inside my iframe right now). I need to stay in my own website.
I am going to band my head against the wall, so waiting for you comments.
(please comment if you need to see some code source or sth. else)
Thanks.
That's worked for me:
"Internet Explorer > Settings > Internet Options > Privacy > Sites" and then I added the name of the website inside my iframe, done.
I am working on learning Orchard. I have got my development machine in a state where it will not load the home page. I get a 404 error with this message...
Server Error in '/OrchardLocal' Application 404
I realized that it is because no content item is set as the home page. However, the checkbox for making a page (or anything else) the home page is not showing in the edit page screen.
How do I fix this? I need the Make this a Home page checkbox back or some other way to accomplish the same thing.
Is there a way to do this in the database directly (which I realize is a hack but might let me move the ball forward on the problem).
I thought I would mention the EXACT exception thrown by the error is "The controller for path '/OrchardLocal/' was not found or does not implement IController."
Any help is appreciated. If I can't figure this out it seems I will be back to doing Orchard from scratch (new pull, new db etc) which seems to happen EVERY time I try to learn Orchard.
Here are the Parts I have on the Page Content Type. This is probably not the default list because I have been messing with it to get it fixed.
Common
Publish Later
Title
Autoroute
Body
Containable
Navigation
Identity
Menu
For the record I added the blog Module to the site and added a blog. But same behavior when I create a blog...no Make this the Home page and no way to set the permalink.
Do you have the AutoRoute Part attached to the Page Content type.
Check to make sure that your User has the permissions to set a content item as the homepage
To set an item as a homepage just set its permalink to an empty string.
I am using version 14.67.9 of TembeddedWB in a project in delphi 2007. I use TembeddedWB in combination with loadfromstring. That all works like I want it to but when clicking on a link in the page it goes to a page I am not expecting. If for instance the page is on a particular IMDB result site and one clicks on the link the browser goes to about:/title/tt1041829/. I guess I forgot to set some extra property or I am doing something else wrong. If somebody here can point me in the right way i would appreciate that.
It looks like the browser's current URL is not updated and the default "about:blank" is used. I guess this may happen when you don't navigate to the web site directly by Navigate or Navigate2 method but load the HTML from a local file or stream.
Edit: I see, you are using LoadFromString which confirms that.
In that case, it should be possible to use OnBeforeNavigate2 event to fix the URL.
The problem is that the web page you are accessing uses relative links and the reference point that it would be relative too is your loadfromstring which loads through the "about:blank" page. Another way of fixing this would be to inject a <BASE href="http://www.originaldomain.com/originalpath"> tag in the HTML header (between the <HEAD> and </HEAD> tags) which points to the location the page was accessed from. This will tell the browser where relative tags start from and will fix the problem without requiring inspection of every link.