I am simply adding Web Content to my portal and trying to display some simple text, Easy Stuff!
However, I've noticed that if I make the web content large (i.e., 80 lines of text instead of 40), it displays nothing!
I can't figure out the reason for this, has anyone else ever had this issue?
Cheers!
-Running Liferay 6.1.1 GA2 on WebLogic Server 12c
I had the same problem. I redefined in portal-ext.properties the following property:
com.liferay.portal.upload.LiferayFileItem.threshold.size=262144
You can control the limitation of content size by increasing this value to a higher number. The value is in bytes.
Related
Recently none of the web content in the global site is showing up when selecting the web content in a web content display. Nor does the search find the particular web content I'm trying to use.
I assume it is an index issue, but I've reindexed everything I could think of that would be related - everything journal article related as well as document lib related - but nothing has worked. Restarting Liferay hasn't helped, nor has re-publishing the web content. Permissions are unchanged.
Any ideas? Can anyone tell me which indexing option should work?
Liferay 7 GA7
Thanks.
I need to obtain a property that is set in portal-ext.properties from my theme's portal_normal.ftl file. Using Liferay 7.
All my searches have come up short, but I can't believe I'm the first one to have this need.
For background, I need to display a web content that is stored in the global site. This needs to be displayed on every site, which is why it's going into the theme. It also needs to be updated by the content editors, so the content can't be included in the theme.
I can display the web content easily, using the journalArticleLocalService like this
journalArticleLocalService.fetchArticle(10197,"1260480")
but I obviously don't want to hard code the group ID and article ID like this; and they are already stored in portal-ext.properties for another reason.
Also, I know about theme configuration values, I use them for a lot of other configuration needs, but those require the values to be entered for each site and there are hundreds of sites in our implementation so this is not an option.
Thanks in advance for any solutions or advice you can provide.
Properties are (as far as I know) not available in Liferay's Freemarker Templates - and as everything in Liferay tries to phase them out in favor of OSGi based configuration) I'd not recommend keeping up the configuration there. Any change requires a restart of the portal - proper configuration would make them hot-changeable.
However, as you now have this situation and probably look for a quick solution: You can create a TemplateContextContributor and make the required values available for your template.
I've recently started working with portlets, and trying to have experience with several portal engines. I have a basic hello world portlet (extending GenericPortlet and basically doing the same as in all tutorials) that works perfectly with Pluto 2.
I deployed the same portlet to Liferay 6.0, and added it to a page in the portal. Strangely, the portlet frame appears without any content. According to the logs, the portlet init() is called, but doView() is not, thus there's no portlet content in the resulted HTML page.
My question is: should the same portlet work out of the box with Liferay, too? If not, what non-standard descriptors are mandatory for deploying a portlet to Liferay? If yes, what may be the problem? I've seen portlet content height issues mentioned in some forums, but this may not be the problem: the content is not hidden, it's not generated at all.
While checking the relevant file contents to paste here as asked, I realized that my web.xml is empty (as it should be according to Liferay tutorials), but a maven plugin generates pluto-specific invoker definitions into it as defined in my pom.xml. As a result, the generated pluto-specific PlutoInvoker mappings screwed it all up. So it was solved easily, thanks for reading the question though.
Put a relative URL (no server name) into the HTML Editor and save the page. The URL is converted to an absolute URL (http://server_name is added to the beginning).
This is posing a problem for moving content from our staging to production environment, as the server names are different.
The exact same scenario is common when using the Content Editor Web Part, and Microsoft has published a fix here:
http://code.msdn.microsoft.com/WssCewpLinkFixup/Release/ProjectReleases.aspx?ReleaseId=2210
The solution creates a custom ASP.NET 2.0 control adapter to change the rendering process of all Content Editor Web Parts in the application.
But we are using the HTML Editor Field Control, not the Content Editor Web Part.
Can the same approach be used to change the behavior of a web part?
Has anyone else encountered this problem and solved it? A Google search has come up with no answers, only many frustrated users and abandoned forum threads, including this one on StackOverflow from a year ago:
Publishing HTML Field Control Converts Relative URL to Absolute URL
Many thanks in advance.
You may be able to put a little bit of JavaScript in the link, either
Link
or
Link
Haven't tried it, but it may work.
I am having an issue with the drag and drop of webpart in sharepoint. The following described what I have done:
I am using MOSS 2007.
Created some custom page layouts that's based on the original BlankWebPartPage.aspx and tweaked to matched our HTML carve.
Created custom web parts.
attached those web parts to the pages that's based on the custom layout.
Now the web parts are working fine, except for the part that it cannot be dragged and drop to other web parts container on the same page.
If anyone can show me:
1. How to diagnose the issue on what's causing it?
2. Is the drag and drop supposed to work on a custom layout?
3. What's the error that's causing it not to work?
Thanks in advance!
Is this the issue you're experiencing: http://blog.mastykarz.nl/css-causes-javascript-error-while-moving-web-parts-in-edit-mode/?
Yeah that's the one exactly! There is another link in there:
http://neilmosafi.blogspot.com/2007/11/sharepoint-dragging-webparts-causes.html
That link shows a javascript to fix the issue.
You might try dragging into the "add web part" portion of the container of zone. I've had issues with dragging the web parts into position, particularly custom web parts.
Also, can you post some code? Particularly the page layout. Feel free to clip out the most non-essential parts, but it should help to diagnose your problem.