occasionally when hitting the landing page after signing in, the users personal space is displayed instead of the default guest page. This is does not happen often, but my boss does not want it happening. I am hard pressed for an explanation.
This is not really programming related - the liferay forums would help a lot better with that problem.
Other than that liferay tends to remember your last visited page - which bit me more than once when one part of the site was included in an iframe portlet - the iframe content was the remembered "last" visited page, not the one containing the iframe. After Login, that was the target.
As far as I know the personal pages are shown after login if the desired landing page (or the last visited page) was not found.
You can disable the redirect to the last visited page after login by setting auth.forward.by.last.path=false in portal-ext.properties
Related
In a project repository, I created a Wiki, but have renamed "home" to something else. Now, when I go to the Wiki again, it asks to create a "first" page because "home" does not exist; is it possible to specify the landing page for a project's Wiki (i.e. change "home" to something else per project)?
It is not possible (as of 14 Aug 2020). See documentation on the wiki.
The /home page appears to be the default wiki page, and if it is not created it seems that Gitlab will encourage you to create it every time you click the Wiki navlink. I tried myself to create a home page in a Wiki on Gitlab, delete the home page, then click on the Wiki again, and GitLab wants me to create the home page (although the other page that was renamed is still there).
What I recommend is to use the /home page as the landing page, and put a link to your other page on the /home page.
It does seem that this issue has been raised before, however, the GitLab team has yet to implement it as part of their codebase:
Old, original Feature Request
Open Feature Request (maybe this feature will be released soon)
I suspect that in the past, the default landing page was index.md, as indicated by these public-facing company GitLab landing pages, but there was still a forced default page:
Example 1
Example 2
So I am new to SharePoint 2013. I created a site page (web part page) and made that page into the homepage . Everything worked fine but when I click on the logo of the page it takes me back to my older homepage. I even went to site settings, Title description and logo to change the web address, however, it doesn’t allow the site pages to be on the web address. It doesn’t let me add “/“ to the url of web address so how do I fix it?
The logo URL is usually set in your master page. If you don't have access to SharePoint Designer or you want a less invasive approach, you can always try this option:
https://support.office.com/en-us/article/use-a-different-page-for-your-sharepoint-site-home-page-35a5022c-f84a-455d-985e-c691ab5dfa17
Basically, you choose which page you want to be your home page. This might work for your situation.
I have created my gravatar profile and added websites from websites tab.
Now I want to delete some of my websites but I can't.
Please see the attached screenshot.
when I click on delete button on left of the website, it removes from the list but when I again come to my website page, it remains the same.
Please help me remove unwanted websites from my profile.
The gravatar information (as most of the content on large web sites, also the content on Wordpress.org/.com) is cached.
It may take a while the information to be refreshed. However this is not Wordpress specific question, if you experience the issue after a while (usualy a couple of hours), consult the gravatar FAQ/support.
I have a fairly simple page in WSS3. It's basically a web part page with a custom webpart to display some text and a embedded video from Vimeo, a custom webpart to handle newsletter submissions (a simple form) and a couple of document libraries.
I'm using Forms authentication. My admin user can sign in and browse the rest of the site with no problem, but this one particular page causes the user to be presented with a blank white screen. If I view the source of the page I can see the correct markup and the issue only occurs in IE.
When browsing the site anonymously there is no problem.
Does anyone know what could be causing this?
It sounds like a javascript problem to me - the document library view will render extra menus etc. if you are an authenticated user with some contributing rights to the site. It's probably these that are colliding with something else and causing your issue.
As you'll have no control over the document library viewer web part, I suggest you remove your custom web parts from the page (with the document library viewer on it) and readd them until the page breaks.
I had a similar issue at one point in that we were overriding some functions that were in a SharePoint js library, however as the SharePoint file was registered at the bottom of the master page and ours were in webparts (which loaded first but were subsequently overridden by the OOB file), we had some unexpected behaviour. I fixed it in the end by adding our custom part to the master page after the OOB file was registered.
I have a feature that deploys a few site columns, a content type (inheriting from Page Publishing Content Type) and a page layout based on my content type.
Everything is fine on two tests, performed on different servers, but on the third server, although the feature is being activated correctly and I can see the site columns, content types and the page layout in the galleries, I cannot create a new page based on my page layout because the page layout does not appear in the list of available page layouts.
On all tests I have used the administrator account.
Does anybody have any thoughts on possible reasons for this?
Thanks.
Did you have a look at the "Page layouts and site templates" page under Site Settings? On this page you can enable an option that limits the available page layouts to a specified list of page layouts.
I have worked on a project where we needed to limit the page layouts available on a custom site definition. We implemented this in a feature, that enabled the "limited page layouts" option and populated the list of available page layouts upon activation.
If this is the issue you are having you could simply turn off this option in the web interface or add the new page layouts manually, but you could also consider implementing a feature receiver that automatically adds your custom page layouts to the list of available layouts.
Thank you all for your answers.
What actually happened is that the page layout was, for some reason, deployed as a Master page and not as a Page Layout. The admin has manually changed this and now it works.
This is just an educated guess but check to see if the Page Layout is waiting to be checked-in or approved.
In my case the path for the layout was wrong so the layout itself ended up in a different location, when I corrected that i was able to see the results.
I had added files manually and it did not appear.
When I edited properties of that layout page from UI and saved it, it appeared.