Kentico 9.2 modify administration pages in WebApp - deployment

i just modify an file from kentico CMSApp project.
The path:
CMS\CMSModules\Content\CMSDesk\Properties\Menu.aspx
i change an input from cms:CMSTextBox to cms:MediaSelector.
In kentico dashboard -> pages -> Properties -> Navigation
After that i deploy the CMSApp_MVC project, and copied the files from the folder i mentioned.
Now it doesnt work on production environment.
Help please.

It is highly recommended not to modify Kentico system files unless you have no other options. Your current change is not supported and instead of doing that I would recommend to create a Custom page type field using whatever Form control you like to hold your value - just don't change the file you mentioned directly.
You can then work with that field just like you would with any other Document/TreeNode field.
PS: Kentico 9.2 does not exist.

Related

Howto to configure TCA settings and save them globaly

I'm configuring a new website with TYPO3 v. 9.5.
I would like to configure TCA settings to make it possible to force editors to fill fields in content elements like media or news.
In former times I was able to put this settings into a file typo3conf/extTables.php.
In my investigations I found, that I have to put configurations into a directory Configuration/TCA/Overrides of an extension.
I tested it with the extension tx_news like this:
I put this code in a file called test.php as a test and example.
This code forces the editor to always enter an archive date.
This works for me, but after an extension update, this code might be lost and I cannot configure the fields of core extensions for example to force an editor to always enter a title of a content element.
My question is, how can I store this configurations update save within the configuration environment?
Thank you in advance,
Ralf
Depending on your modifications you need to consider some aspects:
always use a filename according to the table your modifications belong.
so for the news records it should be: Configuration/TCA/Overrides/tx_news_domain_model_news.php
make sure your modifications are loaded after the first initial configuration: make a dependency to the original extension.

AEM 6.3 Communties CKE editor config local file

i'm attempting to update the UGC toolbar for a Communities implementation. Based on this: https://helpx.adobe.com/experience-manager/6-3/communities/using/rte.html I can update the toolbar. Ideally we'd like the ckrte.js to site within our code base. I've tried within our clientlibs in our project folder but that didn't work.
Can this file live local, or will it only work in CRXDE?
You can copy the file and add it to your code base and ensure that it loads after the out of the box clientlib has loaded. They register the rte as "ckeditor" in the JS, your code will override the previous registration. Saves the hassle of modifying the original file that might get changed during upgrades or service pack installations.

TYPO3 template extension- not able to change Mask back-end configuration and Page Tree not properly imported

I have created a TYPO3 template extension using the following method:
1.1 via Extension Manager
Open the module "Extension" in the TYPO3 Backend and search for the mask Extension.
Click on the configure icon at the end of the row.
Now you should be able to change the settings.
Changes are stored in typo3conf/LocalConfiguration.php.
Facing the following problems:
1.We created the folder/extension as mentioned. While installing this extension we have to change Mask back-end configuration. This is not working.
2.Page tree contents are not properly imported i.e. all page contents are missing.
Please let me know if you need further details.
We have a working configuration where we stored the full mask-configuration as part of our site-extension.
As designed you need to configure mask before you start to define any CEs, so that all CE definitions are stored in the correct folders.
For the rendering you also need to include the static template of ext:mask.
Our configuration is:
This configuration is stored in typo3conf/LocalConfiguration.php as there goes every configuration done in the extension manager.

How to create custom template of Typo3 bootstrap_package

I am quite new in typo3. I read somewhere
You should never edit the original templates of an extension as those changes will vanish if you upgrade the extension
How to create my own custom template based on bootstrap_package extension? I would like to override some files in parital/layout. It would be great if someone can post like/tutorial.
A folder structure and a simple custom typoscript that implement bootstrap_package for my custom temple would be great help.
The bootstrap package developers already added something for this. It is possible to set different locations, where templates are stored. It also uses a fallback solution, that means if a template is not found, it will fetch the original one from the extension.
Create a directory in the fileadmin directory, for example fileadmin/templates/BootstrapPackage. Inside this directory, create the directories "Templates", "Layouts" and "Partials".
In TYPO3 backend, go to the constant editor of the root page and select everything like the screenshot says:
Set the fields "Layout/Partial/Template Root Path" to your new created directorys (fileadmin/templates/BoostrapPackage/Layouts|Partials|Templates). Save and clear the cache.
Now you can create new templates. If you place an exacly named file like it is named in bootstrap_package/Resources/Private/(Layouts/Partials/Templates)/Page/ , TYPO3 will use the new template instead.

Custom fields are not exported using Studio's exporting tool - SugarCRM

I'm experimenting an issue when I export customizations made by Studio tool, any custom fields are not exporting. I mean, when I load the package created in developer server to the production server, there are not custom fields in EditView, there are "native" fields only.
I'm using SugarCRM 6.1.6 (I know, it is an old version, but I can't update it right now)
Regards
Mauricio M.
You may just need to do a repair and rebuild - that's the likely quick fix. Alternatively, ensure that the package on the dev server exported both the custom fields and the custom layout metadata (i.e. the edit and detail view layouts). If it did, double check the permissions in custom/modules//metadata to ensure that the files were able to be uploaded and are readable by the web server.