File assciation screen is not updated when components are re-selected - install4j

I have an install4j installer with multiple components. For each component, a file association is registered with the proper condition:
context.getInstallationComponentById("1").isSelected()
After the user selects the components, he gets to the file associations screen, where - correctly - only those file associations are offered that fit the selected components.
When the user goes back some screens and changes the selected components, however, the file associations screen is not updated and still shows the previous list of associations.
Can I force an update on this screen somehow?
I am using install4j Windows Edition 6.1.1 (build 6254).

This is currently not possible and will be fixed in 7.0.10. Please contact support#ej-technologies.com to get a pre-release build.

Related

Get Sitecore item's publishing settings by version with PowerShell

Problem
I'd like to be able to get Sitecore Item's Publishing Settings by version to check whether a version is publishable or unpublishable.
Supporting Details
This can be viewed in Sitecore by navigating to the item, clicking the Publish tab, clicking the Change to view the Publishing Settings, and then in the Versions tab, checking whether the current version is publishable or not.
Attempts
I can get the item tab's publishable value, but not the version's.
(get-item -Path "master:/sitecore/content/...path to item").Fields["__Never publish"]
I've also looked through the available fields and done some searching, but can only find the item's publishability.
Look for __Hide version field, it controls an item version publishing. If its value for a certain version is 1 then that version will be prevented from publishing, if it doesn't have any value / empty then the version will be published as usual.
Also, note that __Valid from and __Valid to fields are responsible for the version publishing.

how to put a comment while creating a version in aem 6.1?

I want to put a comment in a particular version of a page.
It gives an option to put the comment but its not specific to a particular version.
Is there a way to put the comment while creating the version in AEM6.1?
You Can always create a comment while creating a page version from your Sidekick "Versioning" tab
Good Observation. As per the Adobe Documentation AEM 6.1 working with page versions These are the steps to be followed to created the version of the page.
You can create a version of your resource from the timeline tab:
Navigate to show the page for which you want to create a version (In fact it is parent level).
Select the page in selection mode.
Open the Timeline column.
Click/tap on the arrowhead by the comment field to list the options:
Select Save as Version and confirm with Create.
The information in the timeline will be updated to indicate the new version.
And here i have noticed that the comments pushed via touch UI is not considering while Version node creation.
A little close observation at the node version properties that got created for the Classic UI vs Touch UI versions for the page. The cq:versionComment is missing (not created) for Touch UI process.
The verions 1.0 and 1.2 has created with touch UI and version 1.1 created by using Classic UI

How Avoid Muliple checkout of Componentes in AEM page other than Pagelock

My Requirement is like Build in a process to lock a component during content development or updation.
For example, Vivek can still publish a page with OLT update while another author is updating another component in the same page. The previous version (that is not being updated) will be published along with vivek’s updates.
Since the User group is large & we have frequent updates we can't go for Pagelevel lock(multiple user will be working on the same Page).is der any Possible way to achieve this?... i hav tried the "FieldEditlockMode" but not works for me,am using AEM 6.1
Thanks
AEM Launches may satisfy your requirements, allowing your authors to edit components for future production releases without affecting an immediate release. Here is the documentation for 6.1:
Launches
Creating Launches
Editing Launches
Promoting Launches

Issue with publishing a new page in CQ5

I have installed both author and publish instances of CQ5.5 on my PC. But when I add a new page and publish it, it does not appear in the publish instance. Only a blank page is rendered.
I have tried activating it both from the siteadmin and from the Replication page in Tools. Only the navigation item appears in the Publish instance.
I checked the Request logs also. But it only gives a
200 response(OK)
Can someone please help me on this ?
You need to activate/replicate your /apps/site folder where all of your templates and components are located to push it from your author instance to your publish instance. Activating a page doesn't automatically activate the components and templates it uses.
Go to:
http://localhost:4502/etc/replication/treeactivation.html
Browse to or type /apps/[your site] in the path field
Set the check boxes to fit what you want to activate (Unchecking all will make everything under the selected path activate)
Click 'Dry Run' to see what will get activated without actually activating. (This is more of an informative step to help ensure you don't activate something not intended in a production setting)
Click 'Activate' to activate.
You can then check your publish instance to see your templates and code are there.
It is easy to miss activating your apps folder as there is no ui like the website admin for pages where you can activate.
Activating a page/folder/asset does not activate sub-pages/folders/assets. This can cause confusion especially when working with folders.
Generally if you need to activate a tree the best way is to use the tree activation utility
The only time I've ever seen this is when the code is not installed. That would be the first thing that I'd check. Go to (assuming you have your publisher on port 4503)
http://localhost:4503/crx/de
You should have your the code in /apps and you should be able to find the content page in /content too.
The reason this happens is that the sling:resourceType property points to a component that doesn't exist so it uses the default which is an empty output.
You have to build the code to both the environments (author as well as publish). This way both the environments will have the same copy of source code installed in the form of cq5 packages and felix bundles. Then if you create a new page or drop any component on any existing page, it will appear the same on publish environment after activating the same either through 'Activate Page' link in sidekick or through replication tree activation page.

Libre Office Writer: Strike-out on delete rather than remove?

We occasionally see revision-suggestions for documents (usually from our attorneys) where removed content gets color coded and has a strike through it. Added content also gets its own color coding.
I had always presumed that some specialty software was used to achieve such versioning effects, but one of our salespeople just received a document from their customer and it seems to be in that "mode".
When he tries to delete anything, it simply turns lime green and gets stricken out.
Is this a feature that can get turned on/off in Libre or Open Office?
If so, where/how?
Main Menu - Edit - Changes submenu
This feature is called Track Changes and it allows you to pass documents back and forth and see who made changes. The feature is accessible under the Edit -> Changes menu. Within this menu are 6 items:
Record
Protect Records...
Show
Accept or Reject...
Comment...
Merge Documents...
I should mention I'm using LibreOffice Version 3.6.4.3 (Build ID: 2ef5aff), but this menu should be identical in previous versions as well as OpenOffice.
You can see other peoples changes by checking/unchecking the Show item. If you want to disable/enable the recording of changes you check/uncheck Record. Finally if you want to incorporate other peoples changes you check/uncheck Accept or Reject....
Here are some additional resources to get you started if you want to actually do more than just disable this feature.
Collaborate Using LibreOffice Writer Changes and Comments
Recording and Displaying Changes
Screencast demoing Track Changes
Taming Apache OpenOffice - Tracking changes
LibreOffice 5.4.1.2.0
Edit -> Track Changes -> Record (uncheck Record)