Annoyingly IManage now only seem to give access to the the 8.5x IToolkit, I know there was a much better 9.x version under Interwoven that had a pdf with the commands and context items well documented, but they say that is not available. So I am a little in the dark with this now.
I want to perform a document checkin that shows the newer extended dialogs after the disposition is selected. IManExt.CheckinCmd is only showing the older ones with the context items that are listed in the 8.5x documentation. Can anyone please tell me the context item to enable the newer dialogs, or do I have to use a differing command?
Related
I'm preparing myself to work with the new version of TYPO3 (v10), and I need clear documentation which presents the changes between the old and new version (especially disappear of ("switchableControllerActions")
So if anyone has an idea I'll be grateful
Thanks in advance
There always (for all major versions) are slides "What's new" and a search gives this page: https://typo3.org/help/documentation/whats-new
the other option is the change log / Release Notes for each bugfix version:
https://get.typo3.org/list/version/10
And all together in one page: https://docs.typo3.org/Home/WhatsNew.html
Apart from the answer given, I would recommend the Changelogs in any case. The "What's new Slides" do not contain all changes. The changelogs contain all relevant changes as each change in the core with a deprecation or breaking change must include a Changelog. Also, the Changelogs contain a migration path and tips that should be helpful for you.
I admit, it is a huge long list. So here are some additional tips:
Since you mention switchableControllerActions: For your own extensions, you can use the extension scanner to search for deprecated or breaking functionality in your extension before moving to the next version: In the backend: Upgrade > Scan Extension Files
Also, since TYPO3 9, you can view and check off the changelogs you already handled in the backend, see Upgrade > View Upgrade Documentation in the Backend.
If you want to find out about changes even earlier, you can follow the changes via one of these sources and read them as soon as they come out:
https://typo3.slack.com: channel #rst-updates
https://review.typo3.org and read the core patches and follow the discussions
twitter: https://twitter.com/t3git_master
What I am also sometimes missing is a table with comparison of old and new. But there are some good resources for specific things, such as:
migrating to "new" doctrine QueryBuilder from $GLOBALS['TYPO3_DB']
About the what / when / why of some particular changes: The changelog explains it quite well, including a migration path. What is sometimes missing is, why a change was made. There is also often some more information and discussions in the review on Gerrit. To find that, click on the link to the issue in the changelog and then find the link to the review (should start with https://review.typo3.org) in the history.
I'd like to know where to find a "table" that lets me know if a specific opcode is compatible with a specific version of the IBMi O.S.
Example:
LEAVESR introduced in V4R4
Is there anything like this?
This may be of use to you. This page is a list of operation codes available to the RPG compiler in IBM i 7.3. There is a dropdown towards the top that let's you select a different OS version.
This would allow you to compare operation codes between OS versions.
You can also use this What's New page to see every version back to V3R2.
I'm not aware of anything quite as specific as your question, but all elements are documented in a similar way in the ILE RPG Reference manual. The link is for ILE RPG for IBM i 7.3, but earlier releases have the same section according to the release. So, having just the latest gives you essentially the complete list of changes for all releases.
If you download a .PDF every few versions/releases, you can have a full history of "What's New" even if some future release truncates the section. If you think over the latest section, it should become clear that just having new op-codes isn't totally sufficient.
I'd like to be able to detect which release channel of ChromeOS or Chrome a user is in from inside my chrome platform app. Is there any way to do this? The information is in chrome://version
navigator.appVersion of course gives which major chrome version I'm running. I would be fine with having to make an XHR to some webpage that lists the current ChromeOS versions. But I cannot find such a table anywhere. It would be nice if it were on http://googlechromereleases.blogspot.com/
You can probably use http://omahaproxy.appspot.com/. The main page has a table mapping versions to channels, and the "data feeds" section has machine-readable (CSV and JSON) versions of the same data.
What exactly are you trying to do? Tying app behavior to a channel is an anti-pattern, as the channels are constantly evolving. If you are interested in restricting functionality to a specific new feature, then use minimum_chrome_version in your manifest, or if you don't want to restrict availability of your product during the (generally) brief window between dev and stable, simply parse navigator.userAgent (or navigator.appVersion, as you say) for the Chrome version, then switch your app's behavior based on whether you're before or at the version you need for the functionality in question.
Again, don't require a specific channel. It frustrates users and is a maintenance headache for you.
We are editing lots of pages with text in Confluence version 3.5 but in one good day, we decide to upgrade our system to version 4.3.2. As a result, now, we have big problems with data.
All links in projects start being invalid and markup of text-fields changed, I think it connected with major changes in Confluence.
So now I trying to find way how to update this data and return nice view.
Is there any plugins? Or scripts? Or any default features of Confluence to doing this work.
New Editor
The Wiki Markup editor has been removed in Confluence 4 and replaced with a new XHTML-based editor.
Confluence 4 introduced a Brand New Editor with macro placeholders and a macrobrowser.
By default you won't see wiki markup anymore in the edit mode, but placeholders. There is one wiki macro called Wiki-Markup which u can use to enter wiki markup.
And for users who are very familiar with wiki markup there us an Autoformatting feature, which lets you type wiki markup into the editor and it will "auto-format" the text on the fly.
Have you read Planning for Confluence 4?
Also, please take a look at Migration from Wiki Markup to XHTML-Based Storage Format
Regarding your macros you may try
Re-running Migration or
Re-attempt Migration
The most common reason for content to be in this state is that a non
4.0 compatible macro (or unknown macro) was found on the page.
There are two possible fixes for this situation -
Install a 4.0 compatible version of the macro. See Plugin Development Upgrade FAQ for 4.0.
Edit the page to no longer use the problematic macro.
So as stated i would suggest you look for compatible versions of the macros/plugins and force a re-migratition:
URL: /admin/force-upgrade.action
URL: /admin/unmigratedwikicontent.action
What do you mean by the links are invalid?
I wish to create a document repository for my company. Reason is because my company have many documents and they did not have a version tracking in place. This means everyone is using different version all the time.
Plone is something new to me and i got to know from a good friend of mine. And too bad he is not around anymore to answer my question. I believed in him and i wish to materialize his idea, to use Plone as a document repository for my company.
I have install Plone and manage to view the default Plone page, add all company's username and change the logo to my company's logo. And now the biggest question is, how to setup the document repository? What i have in mind was to create a "page" for the user to add files, download files, search for files and read its description.
Any lead for me to go about?
Reusable,
Same problem here. We started to use Plone as our main DMS 4 weeks ago (inserting existing docs at present).
For working copies, we use iterate (insert plone.app.iterate under eggs in your buildout.cfg).
For versioning, Products.CMFEditions. I believe this worked out of the box.
For creating new workflow, look into plone.app.workflowmanager and read the docs.
In a previous question we asked, we were still looking at Dexterity which has alot going for it but eventually we decided on adapting an existing content type based on Archetypes.
As for inserting files, as long as the description is ok, they will be found through the in-built search functionality, but you might consider using Iterate mentioned above to make sure that nobody is using the same file twice.
As your new, as I am, the docs seem hard at first but are actually quite good.
And this book is still giving me the foundation we need to keep adding functionality.
Good luck
I think, you should get pretty far with vanilla Plone installation, without developing your own extensions or other customization add-on-products. Therefore, I'd recommend you to start with Plone 4 User Manual to find out everything you could do out-of-the box.
As #Speediro mentioned, versioning support comes built-in for the main content types (and you don't actually see CMFEditions mentioned anywhere), but it's not activated for file uploads. Although, as briefly mentioned in the manual: Content items can be configured to have versioning enabled/disabled through the Site Setup → Plone Configuration panel under "Types".
Working Copy Support (plone.app.iterate) should also be there already waiting for activation on Site Setup's add-ons-panel.
Yet, before the Plone Collective (=community) Developer Docs or Professional Plone 4 Development, I'd recommend Practical Plone 3. It has a bit outdated graphics (because it was made for Plone 3), but it's great next step after the user manual. E.g. how to define content rules to send e-mails notifications for content updates (still through the browser without coding). Or how to create custom forms using Products.PloneFormGen.
When you really need to write your own code, it'd be time for Professional Plone 4 and the Collective Docs.
If you can't have a developer to manage your stuff, I would recommand to stay on official Plone, no custom code and use only widly used addons.
I mean:
stay on the default theme (sunburst)
use the default plone content types
only customize the logo
activate plone.app.iterate in the addon controlpanel
do not play with workflow because they need to know what you are doing. by default a file has the visibility of it's folder. It mean if you can see the folder you will be able to see all files inside. You can just activate default worklfow for files under the ZMI.
Use collective.quickupload addon
Your database will going really fast to a huge size because Plone is doing indexing and indexing means lot's of spaces. So you will have to handle this as system adminstrator;