Liferay 6.2 introduces in-place editing for blogs portlet with ckeditor. Is there any way to disable it?
About :-
Remove Inline editing for blogs to activate link
Go to your liferay portal folder.
In that change in :
liferay-portal folder⇒ tomcat-7.0.42 ⇒ webapps ⇒ ROOT ⇒ html ⇒ portlet ⇒ blogs ⇒ view_entry_content.jsp
Search code :
boolean inlineEditEnabled = BlogsEntryPermission.contains(permissionChecker, entry, ActionKeys.UPDATE) && BrowserSnifferUtil.isRtf(request) && !WorkflowDefinitionLinkLocalServiceUtil.hasWorkflowDefinitionLink(themeDisplay.getCompanyId(), scopeGroupId, BlogsEntry.class.getName());
After this code just add this line within <% %>.
inlineEditEnabled=false;
To disable blog inline editing you need to create a hook for blog and override "view_entry_content.jsp" file. In this file find boolean variable "inlineEditEnabled" and change its value to false. Just a note that this change will get applied to across site/portal.
To Overcome this, You can create a display style in asset publisher and override this jsp only when your display style has been selected. This approach will give you an option were you can have a blog with edit enable functionality as well.
HTH
Related
I have multiple language on site , so in Admin panel not work button "Create new" in ger-DE but working in eng-GB
i have no idea what is reason of this issue.
It is my siteAccess for ger-DE
[RegionalSettings]
Locale=ger-DE
ContentObjectLocale=ger-DE
SiteLanguageList[]
SiteLanguageList[]=eng-GB
SiteLanguageList[]=ger-DE
if i will change like this
[RegionalSettings]
Locale=ger-DE
ContentObjectLocale=ger-DE
SiteLanguageList[]
SiteLanguageList[]=ger-DE
SiteLanguageList[]=eng-GB
Than it working. but half of admin panel is on english . what i`m do wrong ?
You need to set TextTranslation option to enabled, too which enables translating the interface. Complete example:
[RegionalSettings]
Locale=ger-DE
ContentObjectLocale=ger-DE
SiteLanguageList[]
SiteLanguageList[]=ger-DE
SiteLanguageList[]=eng-GB
TextTranslation=enabled
Note that you also need to clear ALL the caches for this change to work.
I translate all classes to all languages and it`s work now!
I am attempting to display a project level property on a widget. Global properties work fine, but project properties come up blank.
I am using:
<%= configuration('sonar.projectlevel.prop1') -%>
in the .erb file, where sonar.projectlevel.prop1 is property name. It comes up blank. If I put in a global property instead of the project property,the property is displayed.
When I open the project dashboard and go into Configuration | Settings, I can see the project property and the value. I can also retrieve it using the ws properties api specifying the resource name, so the value must be there.
Should this work? If so, how?
I have also posted this question to the mailing, but have not had a response. Surely this can work and is easy to do. I must be missing something simple.
Thanks, Ben
Simon Brandhof replied to the mailing list question with the solution. To display a project level property in a widget use:
Property.value('sonar.projectlevel.prop1', #project.id)
instead of:
configuration('sonar.projectlevel.prop1')
Thanks Simon!
I'm working with dotnetnuke 7.
I'm not using any rewriting modules and don't want to use them.
When content localization is enabled, url has the following view:
my_training_host/en-us/my-page.aspx
I want to change manually the display url so, that instead of full culture in query, the two letter culture (neutral culture) will show:
my_training_host/en/my-page.aspx
Does anyone have similar problem ?
If you ever change your mind about using a rewriting module, UrlMaster is the module for that. If not, then DNN 7.1 now adds support for creating url providers as extensions. More details at http://www.dnnsoftware.com/blog/cid/154604/Introducing-DNN-Extension-URL-Providers
I am using Open URL Rewriter for DNN - it does exactly what you ask for with it's default installation - no further config required.
And it's open source in comparison with UrlMaster.
In case of you use version 1.3.1 of Open URL Rewriter with DNN 7.04 to get two letters only for multilingual sites you have to make sure:
you create site aliases for each language with the two letter part you desire and
enable those entries as primary aliases (you need one primary alias for each language), for example for two languages (en & fr) you need to set three primary aliases like the following:
✔ www.yourdomain.com
✔ www.yourdomain.com/en us-US
✔ www.yourdomain.com/fr fr-FR
I often need performance information from live sites. Since I cannot show debug information to the end users, I need a way to enable Joomla! debug mode with a URL parameter, that is,
http://example.com/?debug=1
I have only been able to achieve this with a core hack of includes/framework.php at line 91 (Joomla 2.5.9):
define('JDEBUG', $config->debug || JRequest::getVar('debug','0')=='1');
Which alternatively could be played on configuration.php:
public $debug = JRequest::getVar('debug','0')=='1';
I just tested overriding the configuration with a system plugin following Mark Dexter and Louis Landry's post at Using Plugins to Override Core Classes. But a quick-test with Ivan Rajkovic suggestion,
print_r(JLoader::getClassList());
shows that the configuration is already loaded, so it cannot be overridden.
Can you suggest a better way to achieve this without a core hack?
Is there a solution for Joomla! 3?
I think if you enabled the debug plugin (in the plugins list) and set its access level to Superuser or whatever your rank is, no one else will be able to see the debug information except you.
Update
There's a plugin (for Joomla! 1.5 though) that limit the debug output for certain IPs to make it possible for you to debug a live site without exposing it to everyone. Not sure how easy is it to make it work with Joomla! 2.5
I'm currently editing my portal_normal.vm (server/tomcat/webapps/mytheme-theme/templates) testing if I can write on the file and see it on my browser. I tried putting a test comment "<!-- test -->" just to see if I can really write on the file. So I refreshed the file and hope I can see the comment I've added, but there we're none. So I continued refreshing (ctrl+r),\ and viewing the source code for almost an twenty minutes. After a while when I tried viewing it again it reflected in my source code. So I thought it was cached by either Liferay or my browser.
So I tried tweaking the comment adding version on it ("<!-- test v2 -->"), hoping to see changes. I checked it on another browser and the comment didn't update or include my added version. So I think Liferay is responsible for the issue.
this is what my portal-ext.properties contain:
auth.token.check.enabled=false
# Database settings
jdbc.default.jndi.name=jdbc/LiferayPool
#For removing captch
captcha.check.portal.create_account=false
session.enable.phishing.protection=false
default.regular.theme.id=my_site_WAR_my_theme
#Delete cookies while deleting session
session.enable.persistent.cookies=false
#redirecting null problem.
redirect.url.security.mode=mysite.com
journal.template.velocity.restricted.variables=
admin.email.from.name=Market.Travel Team
admin.email.from.address=admin#mysite.com
# Added because of the Error - No Hibernate Session bound to thread, and configuration does not allow creation of non-transactional one here
hibernate.current_session_context_class=thread
session.enable.url.with.session.id=false
and my portal-developer.properties
theme.css.fast.load=false
theme.images.fast.load=false
javascript.fast.load=true
javascript.log.enabled=true
layout.template.cache.enabled=false
browser.launcher.url=
combo.check.timestamp=true
freemarker.engine.cache.storage=soft:1
freemarker.engine.modification.check.interval=0
openoffice.cache.enabled=false
velocity.engine.resource.manager.cache.enabled=false
com.liferay.portal.servlet.filters.cache.CacheFilter=false
com.liferay.portal.servlet.filters.themepreview.ThemePreviewFilter=true
Addition: When I tried editing the css files I can see the changes fast. Just one reload the the changes appear. I think it is just in my velocity template that take some time or there's something wrong.
Liferay version: Liferay Portal Community Edition 6.0.6 CE
Thank You!
There is really no need to define your own portal-developer.properties. By adding -Dexternal-properties=portal-developer.properties to your JAVA_OPTS in tomcat/bin/setenv.(sh|bat) Liferay will use it's default developer settings, which are almost identical to what you have provided. However, I do not believe this is contributes to (or could resolve) your problem. More details here.
The developer properties do allow you to make live changes to the templates provided you are changing the right file. Due to the default context.xml Liferay provides to the deployed webapps, the webapps are copied/cached in tomcat/temp/{id}-webapp-name. This means if you change the template in webapp/mytheme then it may take tomcat a while to pick up on the change, if it notices the change at all (this will depend on the tomcat configuration). On the other hand, if you make a change in temp/1-mytheme it will show up immediately. Editing the files in the temp folder is probably not ideal, so...
How to fix this: (no specific order)
Prevent Tomcat from using the temp directory for your theme. Create a context.xml file for your theme.
<Context cachingAllowed="false"/>
This file should be placed in the META-INF folder of your
theme. If you are using the Liferay auto-deploy feature the
context.xml file may be clobbered, here, and here. If this
is the case you will need to find a work around that best suits your
needs, such as modifying the context.xml after the theme is deployed.
If you are using the Liferay Plugin-SDK the you can follow the fast plugin development guide for setting up your development environment.