I have a portal in Internet, and I would like to register it in sites like Alexa, Quantcast and other similar sites for ranking and web analyzes.
However, in most of the cases I have to put an HTML file inside the portal, however I do not know how, because all uploaded files are web content in Liferay, and the address is not the address that those sites are going to look for.
In other cases, I have to put an extra meta-data tag, but the only one that I can modify is the keywords meta-tag.
I do not know how to put a file specifically in the portal or add a special meta tag in the head section.
Thanks for the assistance.
You can add those in theme of yours. Check out portal-normal.vm to add meta tags in the head section. And you can create a separate footer.vm if you want to include any javascript snippet.
Related
https://azure.microsoft.com/en-us/updates/new-azure-api-management-developer-portal-is-now-generally-available/
Extensibility—The portal comes built into every API Management instance (excluding the Consumption tier). If you wish to extend the portal’s core functionality (for example, create your own widgets to fetch data from other sources), fork the GitHub repository, implement the code changes, and self-host your own modified version of the portal.
Is it so that we can't do custom widgets on Azure hosted Developer portal? If so, then this is a backstep from the legacy portal as there we could write custom HTML and JS to get custom features.
I believe still there are couple of things you can do.
Home page
The default Home page is filled with dummy content. You can either remove the whole sections with the content or keep the structure and adjust the elements one by one. Replace the generated text and images with your own and make sure the links point to desired locations.
Layouts
Replace the automatically generated logo in the navigation bar with your own image.
Edit the content of the portal, customize the website's look, and publish the changes.
Please refer https://learn.microsoft.com/en-us/azure/api-management/api-management-howto-developer-portal-customize and let me know how it goes
You can submit a pull request to the repository.
If you create a custom widget and this will be useful for many users it can be included in the default set of widgets.
I Want to Show custom welcome screen when a user logs in to Dynamics CRM 2016. I searched and i just got how to disable welcome screen tour but i couldn't find how to show my own custom screen (message or HTML).
Any help is appreciated.
Thanks
Make a dashboard with a single large HTML web resource.
Place your content inside that HTML web resource.
Set that dashboard as the default for new users. Display a specific dashboard by default for a specific user role
You can also add your welcome page as HTML web resource, add its link to your sitemap and set this sitemap subarea as a default tab for every user.
EDIT (detailed description):
Create custom HTML web resource and publish it in CRM.
Edit your sitemap to contain link to newly created web resource. Sample configuration below:
Sample
In my case my web resource HTML name is "new_welcome.html"
Go to user's personal options and set your new site.map position to be your user's default tab. You may do this with CRM interface (separately for every user :()) or with the tools for personal options mass update (for example with User Settings Utility from XrmToolBox)
Sample results of above mentioned operations:
Solution of you problem is Announcements.
Its easy to configure and easy to circulate the information across all the users.
Follow the below links for more information about Announcement,
https://www.microsoft.com/en-us/dynamics/crm-customer-center/broadcast-announcements-to-an-entire-organization.aspx
I would suggest not to use announcements because of the following reasons:
It is legacy functionality from CRM 2011 version.
It does not support rich text formatting or html components, images, etc.
You still need to create custom web resource to present it to the end user (so from the work effort perspective it also does not make sense)
I am working on my first shopware project. I need to create a new contact us page on shopware using my own template. My contact us page contains two forms and some other contents.
If someone can tell me how to create a custom template page on shopware I know how to add two forms and the other page contents into it.
In theme folder, there is a folder called “custom” for the content pages such as “about us” . I need to create a same type of page for my new contact us page.
Please let me know if the question is not clear.
You have to create a custom Theme via the Theme Manager in the Backend, the CLI or on your own with a Folder below themes/Frontend/ThemeNameHere and a file "Theme.php"(documentation).
After that you have to create a file at the same place where the one you want to override. In your case below themes/Frontend/ThemeNameHere/frontend/forms.
Then simply name the file like the original file and put in the first line {extends file="parent:frontend/forms/fileNameHere"} and copy the smallest available {block name="specificBlockName"}{/block}. After that you only have to change the selected theme in the backend to your new theme.
I think this is very well explained in the documentation.
Additional you can take a look at Udemy but it is in german.
I have a portal in Liferay 6.2, and need to design the velocity template of a web content that must have a menu listing the pages (linked names) of the site where is present.
My questions are:
Is this possible?
What would be the correct way to do this?
Would it be better to make a portlet instead of a web content for this purpose?
Thanks for the help.
It feels a bit like you are trying to solve many problems in a single template - consider to compose the UI from many different elements (e.g. custom portlets) rather than building the one structure/template that fits all requirements.
That being said, as there's also the chance that your template doesn't do more than just displaying the current navigation: You have two options: The out-of-the-box Navigation portlet is quite configurable, you might be able to utilize that one instead of implementing anything yourself (check the configuration options).
And lastly, if you want to implement for yourself: Get hold of the themeDisplay object. With getLayout() you'll get the current page, while getLayouts() you'll get all pages of the current site and can enumerate them. However, there's one problem: You typically don't have access to the themeDisplay object from a CMS template. But there are several ways to still get to the data (search the Liferay forums for cms template themedisplay). Also, an Application Display Template will be a lot more powerful - and you can also check how the layouts collection is built - just search for usage of ThemeDisplay.setLayouts in Liferay's source code. But with ADT we're diverting from your original question.
Liferay offers a sitemap portlet out-of-the-box which lists pages of a site. You can configure it and define your own application display template (ADT).
I am currently involved in project where we are using Liferay (6.1 GA2).
It seems that Liferay search results provide links to Web Content Fragments instead of to the pages containing them.
Have any of you gone through this issue? Do you know how to solve it?
Thanks a lot pals.
Best, Alberto
You can have a lot more content in the backend than actually displayed on any page. Further, you can display any article on multiple pages at once.
A way to work around this is to specify in the "Web Content Search" portlet that you're only interested in content that is actually published. However, this does not solve your second problem: The content can still be published on many different pages.
Every content can have a "Display Page" - the setup of such a display page is well explained in the UI (see the Web Content Editor) so that you'll actually see a proper page with the search results.
If you actually want to search for pages only instead of content (you might miss out on some metadata), I'd recommend to go with some spider solution that spiders your website, indexes the pages independent of their construction elements (articles) and search that external index.