Extension configuration missing - typo3

Extension configuration is missing for all extensions that should have one. Am I missing a configuration that was introduced in version 9?
1

The Extension Configuration, which was formerly found in the Extension Manager, has moved with the release of TYPO3 v9.
You can change the configuration of extensions now in the new TYPO3 Backend module ADMIN TOOLS > Settings. It's the first box in the list, the title is still the same.

Related

Eclipse Spring Tools missing content assist/ autocomplete

new year - new problems ;)
I'm working on a Linux machine and I've just installed a new Eclipse.
Version: Oxygen.2 Release (4.7.2)
Build id: 20171218-0600
JRE: java version "1.8.0_151"
Java(TM) SE Runtime Environment (build 1.8.0_151-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.151-b12, mixed mode)
Then I've added the latest Version of Spring Tools 3.9.2.RELEASE via the marketplace.
The only other additional plugin that is currently installed is Subversive 4.0.5
The Project that I'm working on and that previously worked as expected has the Spring Boot Project Nature enabled.
But with the new installation I'm missing the autocomplete feature - No completion or proposals of properties anymore.
In the Project Explorer the application.yml display only the standard file icon and no longer the (if my memory serves me right) Spring leaf icon.
In an other Project using a 'application.properties' file the behavior is the same.
Is there a setting that now needs to be set? Or something else that I can check?
Not directly related to my previous question:
In my old installation that worked, I've always wondered why exactly these two filenames application.properties and application-dev.properties (or their .yml analogous) were recognized as properties files while other were not e.g. application-test.properties or application-prod.properties.
See image taken from STS-3.9.2:
It is not only an issue with the icon, but also it opens the wrong editor and therefore I don't have autocomplete support - unless I say Open with -> Spring Yaml Properties Editor.
The answer to the "sub-question" about the application-test.properties file: the content-type that got defined for the Spring Boot property files got defined for specific file names only, since it wasn't possible to put a wildcard-based name like application*.properties in there. But once you opened that file with Open With -> ..., Eclipse will remember your choice for the next double-click.
Future versions of Eclipse (I think it is Photon) will have a more flexible way to define those file name matchings so that we can solve this in future versions.
Follow these steps:
1) Right click on application.properties
2) Open with -> others.. -> search for spring Properties Editor -> tick the use it for all application.properties nd the click om ok.
I analyzed the problem of the missing property editor and found the reason (and a solution for it), which is documented here:
Missing Spring Properties Yaml Editor and and Spring Properties Editor with Spring Tools 3.9.2
Select the file you would like to open, i.e. application-xyz.yml
Open with "Generic Editor - Spring YAML Properties"
Check the box: Open *.yaml files. Click OK.
That's it. All *.yml files icons now become Spring-ish look and feel. And from now on, you open any YAML file automatically with "Generic Editor - Spring YAML Properties"
Code completions work for me when I edit application.yml.
Is your file names application.yml and located under src/main/resources in your boot maben project?
Did you open the application.yml file with Generic Editor:
install spring tool suite 4 from marketplace

How To add custom styling to dnn Default HomePage?

How can we remove default HomePage Theme with Custom Theme in DNN 8? I haven't got any blog providing me clear idea about it.
You can change the styling of a page by changing the "Skin" or "Theme" in the Page Settings on the page.
Update:
To create a skin I highly recommend you follow my tutorials:
http://www.christoc.com/Tutorials/All-Tutorials/aid/8
In order to use the DNN Theme Project template (new with the 4.0 release of Christoc’s development templates, January 2015), you will need to follow the steps laid out in this tutorial exactly. If you choose to not follow each of the steps, you may run into trouble and will have to figure out things on your own. As always, support for our tutorials is provided in the form of paid DNN Support and Consulting. You can also visit www.dnnchat.com and possibly get some free support there, but no guarantees are made that support will be provided there.
Prerequisites
The latest release of the Project templates requires Visual Studio 2013+, it will not work on VS2010 or VS2012.
As with the Module Development templates, the Theme development template requires you to have your DNN Development environment configured in a specific way. You should have your development environment running at the URL http://dnndev.me/ good news for you, it is very easy to do, all you need to do is follow this tutorial.
Once you have your environment setup, you need to install the Project templates. This is another easy step, simply follow this tutorial.
Now that you have the Templates installed, you can get to doing the real work, working with the Theme project template itself.
How to use the DNN Theme Project Template
Run Visual Studio 2013 as an Administrator (right click on the shortcut to do so)
File –> New Project
Choose the Visual C# option from the Languages section of the new project dialog
Select the DotNetNuke Folder
Choose the DotNetNuke C# Compiled Theme template for your project template
For the new project creation screen using the following settings
Name: ThemeName (something unique here, example MyFirstTheme)
Location: c:\websites\dnndev.me\portals_default\skins\ (this assumes you setup your development environment as instructed) DO NOT PUT THE SKIN IN /PORTALS/#/SKINS/
Solution: Create new solution
Create directory for solution : Unchecked (this will cause path problems if checked, the templates assume the SLN is in the same folder as the project file)
Add to source control: Unchecked
Click OK
Once your Theme has been created, you will want to perform the following steps.
After project creation steps
Delete the Documentation folder (it isn’t needed)
Switch from DEBUG to RELEASE mode
Build the project. This will create an INSTALL and SOURCE zip file in the /install folder within the project’s folder on the file system (/portals/_default/skins/themename/install/)
Login to your DNNDEV.me site with a HOST/Super User account
Navigate to the Host/Extensions page
Upload the newly created INSTALL zip file (created in step 3) using the Install Extension Wizard on the Host/Extensions page.
Navigate to a Page and apply the skin to your page.
A few items of Note:
The Theme template and package MUST be in the /portals/_default/skins/ folder, not in one of the individual portal’s (/portals/0/skins/) folders.
The Containers are inside of the Containers folder, inside of the project. This is not where DNN expects them to be, they need to be in /portals/_default/containers/ThemeName/. The Project templates will put them into that location in your development environment when you BUILD the project in RELEASE mode. During Installation in another environment, when installing the INSTALL package for the theme will do the same thing.

The app.server.deploy.dir(C:\liferay\liferay-plugins-sdk-7.0/../bundles/tomcat-8.0.32/webapps) is not valid

I downloaded this, and put it on a folder of my choose. Then, when I try to create a new Eclipse Plugin project, everything goes fine until the "Liferay plugins SDK Setting Page" appears. Then, I'm not able to do anything.
I point to the folder of my plugins sdk page, which is:
C:\Zerok\DevZone\liferay\liferay-plugins-sdk-7.0
And I get the following error:
The
app.server.deploy.dir(C:\Zerok\DevZone\liferay\liferay-plugins-sdk-7.0/../bundles/tomcat-8.0.32/webapps)
is not valid.
After this, I can't do anything. Any help with this?
EDIT:
Check this screenshot: I realized that I was pointing to a 7.0 version SDK, while I have the 6.2, but it fails this way too. Check the screenshot:
You have downloaded a Liferay plugins SDK. In order to have a plugin working, you need to deploy the plugin in a Liferay Server (tipically a Liferay bundle with a tomcat).
The deploy dir is the directory where Liferay will search for new plugins and deploy them.
If have not missed anything from your question, you need a server.
EDIT:
Indeed, I missed something. You have a server (6.2).
First, you need a proper Plugins SDK for Liferay 6.2.
Second, in the build.properties inside that SDK is defined the default properties for building the projects. You can override them with a build.[your-user].properties and set the correct deploy dir there.
Regards
In order for this work correctly in your liferay-plugins-sdk-7.0 folder, you must create a build.${user.name}.properties and in this file you must set "app.server.parent.dir" and point it to the directory that contains the extracted liferay portal 7.0 ga1 files.
app.server.parent.dir=C:/Zerok/DevZone/liferay/liferay-portal-7.0-ce-ga1
Or where ever you have installed unzipped the portal zip. Then try again in the wizard in Liferay IDE.
Note: its better to use forward slashes in your config, '/' instead of backslashes. If you do use backslashes you must use two of them '\\'
gamerson has answered it correctly but I want add some more stuff to this answer.
You need to add a properties file--> build.{username}.properties in your plugin sdk folder.
And also need to add various properties.
app.server.portal.dir = E:\test\liferay-portal-7.0-ce-ga1\tomcat-8.0.32\webapps\ROOT
app.server.lib.global.dir = E:\test\liferay-portal-7.0-ce-ga1\tomcat-8.0.32\lib\ext
app.server.parent.dir = E:\test\liferay-portal-7.0-ce-ga1
app.server.tomcat.dir = E:\test\liferay-portal-7.0-ce-ga1\tomcat-8.0.32
app.server.tomcat.deploy.dir = E:\test\liferay-portal-7.0-ce-ga1\tomcat-8.0.32\webapps
app.server.type = tomcat
app.server.dir = E:\test\liferay-portal-7.0-ce-ga1\tomcat-8.0.32
copy your tomcat directory and place where bold text is.
In addition to gamerson, just create a properties file build.{UserName}.properties file under plugins sdk directory and add only one property
app.server.parent.dir=D:/LifeRay/liferay-ce-portal-7.0-ga3
please note {UserName} is windows/linux username and while specifying property value, use \\ in windows env or / in linux env pointing to liferay home.
please close all dialogs in eclipse and recreate the plugin project again

Custom CKeditor plugin on Joomla installation

I have written a plugin for CKeditor according to this tutorial: Plugin Tutorial but I can't get it shown on the ckeditor's toolbar of my Joomla 1.5 installation. I have copied it in the plugins folder, registered it in the config.js as an extra plugin, even tried the Advanced Configuration in the backend settings by setting this: CKEDITOR.config.extraPlugins = 'myplugin'; or this config.extraPlugins = 'myplugin' but nothing happens, no button whatsoever. Can someone list the "installation procedure" of the plugin on a joomla 1.5 system? Thanks.
You also have to have an entry in the jos_plugins table. Unless I'm building an installation package for it, I just copy a similar record and make the changes to match my plugin - be sure to get the value in the "folder" correct.

Load MCFileManager TinyMCE plugin from external location

i saw in the changelog of MCFileManager the following feature:
Version 3.0.6 (2008-02-21)
Added support for loading the TinyMCE plugin from an external location.
But how can i do this?
When i load the editor_plugin.js file and i enable the plugin in the tinyMCE settings, then i get only errors because the paths are not correct.
In the tinyMCE documentation i've found this:
TinyMCE also supports the ability to have plugins added from a external resource. These >plugins need to be self registering and loaded after the tinyMCE.init call. You should >also prefix these plugins with a "-" character, so that TinyMCE doesn't try to load it >from the TinyMCE plugins directory.
but when i add the plugin using "-insertimage" nothing is loaded.
Thanks for your help,
dattn