Building a Personalized Community in .NET Encoding Code39 in .NET Building a Personalized Community

Building a Personalized Community using barcode writer for vs .net control to generate, create code 39 image in vs .net applications. QR Code ISO speicification Se ing p view c n e n D c men Lib a y d c men s Similar to view count er of the Image Gallery images, the feature of view counter for Document Library documents is not provided in the portal by default. But we can set it up easily by using the following steps: 1. Create a package com.


action in the folder /ext/ext-impl/src. 2. Copy the Java file GetFileAction.

java from the package com.liferay. portlet.

documentlibrary.action in the /portal/portal-impl/src folder to the package com.liferay.

portlet.documentlibrary.action in the /ext/ext-impl/src folder.

3. Locate the Java file at the package com.

liferay. portlet.documentlibrary.

action in the /ext/ext-impl/src folder and open it. 4. Add the following lines after the line String contentType = MimeTypesUtil.

getContentType(fileName); in the GetFile method and save it:. TagsAssetLocalService Code 3/9 for .NET Util.incrementViewCounter(DLFileEntry.

class. getName(), fileEntry.getFileEntryId());.

The code above shows a way to increase view counter for Document Library documents. When called, the getFile method uses the TagsAssetLocalServiceUtil service to increase the view counter for the current document..

Ge ing visi s n b kma k en ies Similar to Message Bo ards threads, bookmark entries have their own model to manage views counter. You can find related methods in the Java file in the package com.


model in the folder /portal/portal-service/src. Open it and then check the following lines:. public int getVisits( USS Code 39 for .NET ); public void setVisits(int visits);. The code above shows the get and set methods for visits. Then check the method to increase visits: locate the Java file in the package com.


service.impl in the /portal/ portal-impl/src folder and open it; check the following lines:. [ 296 ]. This material is copy right and is licensed for the sole use by Richard Ostheimer on 20th June 2009 2205 hilda ave., , missoula, , 59801. 8 public BookmarksEn VS .NET Code-39 try openEntry(long entryId) throws PortalException, SystemException { BookmarksEntry entry = bookmarksEntryPersistence.findByPrimaryKey(entryId); entry.

setVisits(entry.getVisits() + 1); bookmarksEntryPersistence.update(entry, false); return entry;}.

As shown in the code above, it reuses the set method to increase visits (as explained earlier) when a Bookmark entry is opened.. Pe s nalizing se c mmen s Liferay portal provid es Message Boards which can be used to represent comments by categories, threads, and messages. As it uses the discussionId-classNameIdclassPK model, these comments can be used on pages, journal articles, Wiki articles, blog entries, and so on. For example, if classNameId is a journal article, comments are used for journal articles; whereas if classNameId is a Wiki, comments are used for Wiki articles.

You can post comments on pages, journal articles, Wiki articles, blog entries, and so on. Once comments are added, they are visible to anyone. Other users can view existing comments, reply to comments, or post new comments.

It is cool for most of the requirements. But no workflow for approval or deletion is available in this model. For example, a normal user Lotti Stein created comments in a journal article.

These comments will not be published immediately. A CMS admin user David Berger will review these comments first. He may approve or delete them.

Once these comments are approved, normal users and guests will be able to see it. Otherwise, these comments will be deleted, that is, no one can see them anymore. This feature is not available in Message Boards yet.

But in some use cases, we need a workflow for approval or deletion of comments. As shown in the following screenshot, the Approve or Delete workflow was added in comments. For instance, Lotti Stein logged in and posted comments on a journal article.

She could not see her comments immediately. After logging in, David Berger will see and review these comments. He would either approve it or delete it.

At the same time, an email must be sent to CMS admin and/or other persons when comments are created. Moreover, the TO, CC, and BCC email addresses should be configurable and multiple email addresses for all these three fields should be supported as well. The format of email body and subject must be configurable too.

. [ 297 ]. This material is copy right and is licensed for the sole use by Richard Ostheimer on 20th June 2009 2205 hilda ave., , missoula, , 59801.
Copyright © . All rights reserved.