How to create menu on admin menu bar with custom extension? - typo3

I'm new to TYPO3 and I'm building a custom extension. I want to add a menu link on admin panel like web module and list module. Please guide me step by step how to make a new module on admin side?

at https://docs.typo3.org/typo3cms/CoreApiReference/ApiOverview/BackendModules/BackendModuleApi/Index.html you find the step by step guide.
Further I can recommend, to take a look, like other extensions do it. F.e. https://github.com/in2code-de/femanager/
In https://github.com/in2code-de/femanager/blob/develop/ext_tables.php the module is registered.
In line 18, there is there reference to the Controller and the actions, which are allowed
The controller is located in /femanager/ClassessController/ (https://github.com/in2code-de/femanager/blob/develop/Classes/Controller/UserBackendController.php)
Further you need also a html template for each action (look at femanager/Resources/Private/Templates/UserBackend/)

Related

Page option under create menu in sites is not available in my local instance

In my local instance of AEM 6.4, i'm not able to see 'page' option under create menu in sites.
i have created an editable template and enabled it.
what am i missing here ?
I have verified in Vanilla instance also, i don't see this option.
You ll need to create the root page for your site and add the property cq:allowedTemplates. Only then create page shows for the permitted templates.
You have to first create the project structure using the archetype project like maven archetype 13, refer this link for archetype 13, https://helpx.adobe.com/experience-manager/using/maven_arch13.html
This archetype also creates the basic content of a website with root page (example in this case: AEMTraining) and few language pages. Once you have created the project structure and your own global page is available under sites, click on the rootpage. Now, you can see the Page option under create, so you can use your editable template to create
your own pages. (Check the image)

DNN Extensions fail to load DNN 7.4.2

My first DNN site. Please go easy.
I'm trying to load some extensions (Blog & a PayPal extension).
While the admin console show's they're installed I can't see them or start them. They are not evident on any of the menus.
The theme creators say its not their problem.
Any suggestions for a Newby on how to get the extensions working?
thanks
You actually need to go to the page where you want a module to live and then use the Modules admin menu entry to Add New Module to the page. Click the menu entry, and you can drag and drop a module onto the page.
Yes.
They're listed and "In Use" is recorded OS "No"
OK - here's a screenshot of the Admin Page in Edit Mode whilst loggedon as a Super User after an Extension Module has been added to the page.
As you can see:
The extensions are not showing
Instead the area on the page shows 'Banner Options' even though no banners were inserted.
You are on the Admin page, and it certainly looks like you have added two modules to the bottom of the page. One of them seems to be the Banners module, as the screenshot shows that mousing over the edit pencil icon shows the Banner Options.
My guess is that this isn't close to what you want to do.
I think that what you want to do is to add a module or modules to some other pages.
So, go to the page to which you want to add a module. Then, click or mouseover the Modules menu item in the admin menu. Select a module and add it to the page.
Does that make more sense?

add custom editview.tpl for sugarCRM

I change some things in the editview of sugarCRM but I can't find the editview.tpl in custom module accounts.
How I can integrate my new file in the editviewdefs?
For SugarCRM 6.*, if you use Studio to change your edit view for the Accounts module and do a "Save & Deploy" it will place the changes in /custom/modules/Accounts/metadata/editviewdefs.php.
To do even more customization you can edit this file directly as well as create and edit /custom/modules/Accounts/views/view.edit.php. With the combination of both you can pretty much do any sort of customization that you would need for the edit view.

How to add Typo3 Extensions to a page?

I googled for quite some time now and i cannot find a solution for such an easy beginner-problem.
I used the Typo3 Extension Builder to build a test-extension in Extbase. Now i want to use this and include it into one of my pages in the page tree structure to actually see if it works. When browsing the folder structure i can clearly see that the Domain model, the Controllers and all the views have properly been generated. But... How can i tell my page to include it and execute it?
I tried things like including the auto generated typescript into the templates of the pages but nothing works.
Thanks!
In Extension Builder make sure that you added "Frontend plugin" on the left pane. If you'll do it properly you will be able to add this plugin via CE "General Plugin" and then via field "Select plugin"
Sounds like you struggle on a more general level here.
In order to get the output of your Extension in the Frontend you have to assure the following steps:
Set up general Configuration, so that you can see the output of standard content elements in the frontend.
Install your extension and include its TypoScript.
Make sure you have a Plugin configured in your ext_localconf.php and registered in your ext_tables.php.
In the backend, create a new content element and choose "plugin" as its type.
Choose your registered plugin and save.
You should now see output of your extension in the frontend.

How to add custom Web Console Tab in CQ5

I am new in CQ5 and I would like seek help on how will I be able to add a new custom console in my CQ instance. If you guys can give me a walkthrough or a reference which I can use. I'm trying to search for answers but I failed to get one.
You can customize the login and welcome screens by copying the relevant code in /libs/cq/core/content, /libs/cq/core/components, /libs/wcm, etc. to the corresponding /apps node(s), just the same way you would customize an ordinary content-handling component. Some references in the CQ5 docs:
http://dev.day.com/docs/en/cq/current/deploying/configuring_cq.html#Removing%20CQ%20Sign%20Out%20Links
http://dev.day.com/docs/en/cq/current/developing/customize_siteadmin.html