This question was not thoroughly answered here: {{content-for 'head'}} Ember-cli
In the latest version of ember-cli, {{content-for 'head'}} is required in index.html (breaks when I remove it) with zero explanation about it in the docs. I got as far as reading about ember-cli-inline-content here: https://www.npmjs.org/package/ember-cli-inline-content. But where is 'head' defined in the latest ember-cli? Can someone explain this more thoroughly please?
The docs have been updated with a bit more detail on what these hooks are, but the gist is that these are used to allow for ember-cli addons to inject content into the head of your document. They don't offer much beyond that for you to use directly, but they do need to be left in your index.html file so that they are available for any addons you may or may not use.
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 want to set up an open data website with the typo3 cms. For open data I do not know how I can manage with typo3. After a tour on google I found the CKAN API.
My questions: is it possible to integrate them? If not, are there any other solutions with Typo3?
Thank you for your possible answers
I don't know an implementation of the CKAN API and a quick search in the TER (TYPO3 extension repository) never showed any results.
Nevertheless there exists an extension filemetadata which is doing probably partially the requested features. Here the links:
filemetadata on Packagist.org
filemetadata on github.com
For the case that the features are not enough or the structure is not like desired a new extension could be programmed where some basics could be taken from the extension above, at least it could serve as example how some things are done.
It has to be mentioned that some extensions are never registered in TER but only available on github perhaps. So before programming something a deeper search might be advisable.
In former times another extension was common for Digital Asset Management, the extension-key and Name was dam. That extension is not compatible with current TYPO3 versions and taking it as example is probably no good idea as much outdated code had to be adjusted.
Nevertheless the advised example above is not the only possibility, the search for file metadata still shows other extensions that are compatible to current TYPO3 versions 7 and 8 which could be taken as examples. Perhaps changed search-words still let you discover more useful extensions.
The mentioned extension in the top is supported by the TYPO3 core team, the others are provided by other developers. I never compared the extensions and you had to see code or/and features by yourself. So I never endorse any of these solutions as usage is rarely requested.
If you search for the most recent code it's always good to search on github first for the development branch or a release that is not (yet) published in TER. Another source of information is forge.typo3.org, there many extensions are listed too, some even with repository on git.typo3.org, perhaps it's worth it to mention that this source is abandoned by some developers in favor of github.
Technically it would be even possible to extend any found extension and add more features or change something just by another extension - without touching the original extension. But before thinking too far you should first have a look if any found extension could satisfy your needs already.
For further questions that might be already related to coding you should open new question(s) with more detailed explanation and code-examples, even if that doesn't work yet.
EDIT 15th Oct 2018:
Just got a hint about a helpful extension for those purposes: extractor. Additional fields shall go to sys_file_metadata and be a part of the extraction service.
As I never did verified it by myself I can't give further hints in the moment.
When using dashboard (https://melpa.org/#/dashboard) in emacs, how can I set it up so that it ignores directories or filenames matching a pattern like .gitignore ?
For example by default it shows ~/.emacs.d/elpa/*
The emacs community is friendly... but probably not as helpful as they could be. You could try filing a GitHub issue with the dashboard developer (here: https://github.com/rakanalh/emacs-dashboard/issues). If you ever did figure out a fix for your own issue, I bet the dashboard maintainer would be glad to hear about it.
Avoid plugins. Help on opensource plugins is minimal if you are not comfortable with developer jargon, politics and technical skills to understand the source code.
Just wait and see for yourselves - the emacs tag has 5.4K watchers, on average you get about <20 views per question, when do you think the question will be answered ?
Semantics aside, the suggestion is to just use the built in bookmarks feature.
https://www.gnu.org/software/emacs/manual/html_node/emacs/Bookmarks.html#Bookmarks
I am very very new at this so please bear with me. I am a PhD student in Psychology and I am running several online experiments. I took an existing developed github project, adapted it for my purposes and created a url using gh-pages. It worked and here is the url for reference: http://osmp.github.io/sm1/index.html
I needed to create another experiment, slightly altered, so did the same as I did before and used all the existing code as above, just changed the content of some of the text. However, now when I created the gh-page, it doesn't load, see here: https://osmp.github.io/rw3/index.html
As I said I am very new at this so maybe I am missing something very obvious, but any help would be appreciated!
Thanks in advance!
The problem is caused because of SSL protocol.
Github is forcing SSL on the new pages since mid June, as seen here.
As they replied in this similar question try to swap the http js imports to https (they seem to also serve them through ssl) and you should be golden.
I have a lot of coding in FreeMarker template files for view layer in my app.
I was wondering if I can set a debug point with Eclipse. Is there any good plugin that I can use to debug FreeMarker template files?
As far as I know, you cannot. A template file is a plain text file that the template engine reads into memory and then uses to produce a document that it writes to the response. It's not actually executable code. You can put a breakpoint in the template engine code and follow along what it replaces and how.
FreeMarker has a debugging API, although it has stuck in experimental state eons ago, mostly because nobody has taken the effort to write a front-end for it (like an Eclipse plugin). Except, I know they have planned to support it under some of the next LifeRay IDE versions. As far as I know they managed with break points, but there's no support for stepping in the FreeMarker API for example.
This is an old question and answering it right now doesn't make sense, but maybe it helps to all those people who often visit this page to find whether there is a way to debug freemarker or not.
As in the earlier answer it was stated that there is an Official API for the debugging, so just to add a little more into it for beginners.
Please refer to this official API and check freemarker.debug package [as official description says - Debugging API; experimental status, might change! This is to support debugging in IDE-s.], it is surely to help.
FreeMarker 2.3.29