I am configuring a new language version on the existing Kentico 12 website. I can easily create a new culture version of a page by copying content from the already existing language, but a problem is that this feature is available at a page level only what in my case, having hundreds of pages, will results to many hours of manual efforts. Ideally, I would like to select multiple pages and create the new culture version for all of them at once.
Could you please advise me on how I can optimise this task?
You would be able to do it in 2 steps with the help of Translations application.
First, multiple (or all) pages can be submitted for translation via Listing view
Next, select here source and destination languages to copy pages and click "Translate":
Then you will see pages with "Ready for translation" status
Next, go to the "Translations" application and edit the submission:
And finally, click "Export all to ZIP", this will download a ZIP file. Then click "Import all from ZIP" and use the just downloaded ZIP file. Then click "Process translations" and that's it!
Related
I created a flow from the process builder , and I want to sync it locally.
When I looked at the project from mavensmate , I couldn't find the file which is named .flow
This is my first question in stackoverflow , I'm sorry about my poor english , hope you can understand what I described . who could give me some suggestions?
Thanks!
First, you need to update your local SF project metadata. For that, in SublimeText, go to MavensMate menu -> Project -> Edit Project. It should open the project metadata tab in your browser. Click the "Refresh" button and then choose the flow that you need in your project tree. Click "Update project". After that you should be able to find the flow in your project folder.
Go into Mavensmate's settings.
Add ".flow" to the list of extensions under "SALESFORCE FILE EXTENSIONS (MM_APEX_FILE_EXTENSIONS)" if it isn't there already.
You might want to update "SALESFORCE API VERSION (MM_API_VERSION)" to the latest as well.
If your still having problems with that, you might want to check the Flow names including the version numbers. In my case, Mavensmate shows Versions 1, 2, 3, and has no number after the current (active) version. The file on my hard drive is labelled as version 4, so the names don't match up.
To fix this, you'll want to deactivate the processes and update your project.
I manage a team of designers working on Indesign.
When we work on a project, it often happens that a designer has to work on the project of another. We work with Dropbox for Business.
But when we take the work of another designer, there is often missing links and fonts.
Is there a plugin or a way to develop a plugin that would allow, when we create a new indd file (or for the protection of the same file):
Automatically create a "Links" folder and another "Document fonts" at side of the indd file
Systematically add a new link or new typography in the corresponding folder?
To simplify: each action on font or on a link, make a kind of "Indesign Package" in real time?
If this is not a solution, do you have any solutions to meet this need?
I don't know of a specific script or plugin that does this.
However, it should be possible to write a script with an eventhandler with a beforeClose event that runs certain script commands every time a user closes a document (or even every time a user adds, changes or deletes a link). At this point the script could run some copyLink commands on all the images and fonts (?) placing them all in the folders next to the document.
The whole script could be made a startup script, so it becomes active anytime any user runs InDesign.
(I'm actually not sure, if fonts can be copied so easily. Worst case scenario would be that the script would need to run some packaging command to gather the fonts somewhere, copy them over to where you need them and then delete the rest of the temporary package.)
Did you consider Creative Cloud Libraries ? They are meant to allow sharing assets within a team. Apart form that, you users would need to have a same access to the file system (a common drive letter for the network path for example).
Another solution would be to use a DAM solution so users would link files from the DAM.
Eventually, you could sure think of a script as mdomino offered.
It's nice to have a version history in Confluence. However a new version has been created every time when the document is edited and saved. I'm looking more for a "release" history. Assume I have version 1.0 of my document/page. Then I edit and save the page a couple of times before I'm ready with "release" 1.1. I need something to link a version to a release number and then have an automated release history.
Is there a way to do do something like that in Confluence?
I guess Scroll Versions plugin from K15t Software could be one possible solution for versioning and release management of wiki pages within Confluence. https://marketplace.atlassian.com/plugins/com.k15t.scroll.scroll-versions
P.S. I know it is tad old question, but I think someone else may need this info.
A method I have seen used is to attach a file to a page, change the document and upload with the same name multiple times, then change the link on the page when the version changes.
Usually a link to an attached document always references the highest version like this:
[^list.docx]
[ and ] mark the start and end of the link
^ to the right of [ refers to an attachment on the current page
and the rest is the name of the attachment
which resolves to a hyperlink of:
http://wiki.server.name/download/attachments/464233765/list.docx
From the page the full url is more specific:
http://wiki.server.name/download/attachments/464233765/list.docx?version=1&modificationDate=1406619789890
Refer to Tools > Attachments for a list of file version numbers.
Edit the page.
Create a link to the 'next' version with appropriate link text.
[list.docx V2.1|///download/attachments/464233765/list.docx?version=6]
[list.docx V3.0|///download/attachments/464233765/list.docx?version=9]
[list.docx V3.1|///download/attachments/464233765/list.docx?version=11]
As you wrote Confluence always creates a new version once an existing attachment is uploaded with the same file name as displayed on the attachment view.
Existing files will be kept with the name 'Version x', where the value
of 'x' increments with each upload of an attachment with the same file
name.
Source:
https://confluence.atlassian.com/display/DOC/Attachment+Versions
This cannot be changed by configuration in Confluence.
However you can try Arsenale Lockpoint, which is a Confluence Add-on.
Arsenale® Lockpoint™ is the enterprise standard for checkout, checkin
and controlled versioning of Confluence attachments...
Source: https://marketplace.atlassian.com/plugins/com.arsenale.plugins.lockpoint
Arsenale Lockpoint Documentation
EDIT
I have just installed and tested Arsenale Lockpoint and could not find the feature you are looking for
I don't know of any other add-on that would meet your requirements
Therefore i would recommend to edit the file locally and upload it only if you want a new version (release)
A simple alternative to other answers is to use change comments.
When editing page there is an input field next to save button at the bottom. This field has a placeholder "*What did you change?" and its content is shown in page history.
So you can edit page several times and when you want to "release" the version, you can fill the comment with release version. This way you can see all page versions in page history but you are able to easily identify the releases.
See Confluence documentation
While creating a new Portal (dnn 5.6.1) from "portal template" which is created from a bilingual portal(en and tr), all pages(both en and tr) are created in one language. if I activated the second language creates another set of pages for both en and tr pages.
I tried creating a portal template while the second language is disabled but result is same.
do you have any idea to overcome this issue?
My hunch is that, at time of writing, this is an outstanding issue that can't be resolved directly through the UI (I say that because it sounds like you tried every reasonable measure).
If that is the case, your best bet would probably be to edit the generated portal template XML file and remove the elements that represent the second languages pages prior to importing to your target dnn instance. Then you could enable the second language and it would replicate the first language's pages and you could re-localize them. (Hopefully you don't have a ton of pages!).
Alternatively, you could potentially export page level templates for the second language and import them after you've done the import of the portal in the first language. If you take this path, and you have a lot of pages, you may export individually but "bulk import" them by placing them in the /Install/Template folder and hitting the /Install/Install.aspx?mode=installresources URL.
DNN 5.6.1 and i believe also DNN6 has serious issues with exporting/importing multilingual portals. From what i read, the multilingual issue is overcome in DNN 7 which is a major update.
One way to work with legacy multilingual DNN sites is this (far from ideal):
The template which is going to be exported must be in only one language. You may not press the "enable content localization". This is the moment after which export/import becomes very messy.
You export the single language template (this you must keep as the backup point)
Now you import your template.
Then you enable other languages & content localization button (wait till pages are created)
Now you enter the content into the second language pages.
No backups can be created, so you can only backup the content you have entered in the second language, manually..
In any case i recommend you start fresh with DNN7 or a different CMS altogether (WP, Drupal, Joomla...).
Our application is written in C# using .net 2.0. The application tracks our business process and users can attach office documents for reference as attachments. They frequently edit those documents. Currently, they have to save the file to their hard drive, edit and save the file, then re-attach to our application to save into database (SQL 2005).
Our users would like to be able to edit the document and save the changes without needing to detatch, edit, and re-attach.
We can programmatically launch the office (word, excel or powerpoint) document, but how can we tell when the document has closed and re-attach the updated version to the database automatically?
Thanks for any help.
Joe
You may have a designated directory (e.g. Environment.GetFolderPath(Environment.SpecialFolder.MyDocuments)) where you keep the files currently edited and put a FileSystemWatcher to watch whether the file changes.
The Diagnostics.Process class also has an "Exited" event that will notify you when the process, well, exited.
Look into SmartDocument technology at MSDN. Of the three productivity apps you mention (Word, Excel, Powerpoint) the first two for sure, and possibly Powerpoint, can have the right side panel -- where you usually see styles, navigation, or tasks -- programmed through VS using SmartDocument and Tools for Office plugins.
So, you can program the panel such that the user, working in Office or Excel (and possibly PP -- haven't looked into that) can select the document to be edited from your application, do the edits, and save/attach the document, all from the Word interface. The programming behind the right side panel will automagically take care of detaching, and reattaching the document, and can also save the document to SQLServer, if you like.
Hope this helps.
If you are launching the file by using Process.Start method and passing file path as a parameter, you can use the WaitForExit() method to be notified when the user has closed the file.