So, I am creating new section called "My Section" with handle "mySection" via plugin. All good there.
I want to be able for my section to be Viewable via Public Schema each time it is created (when plugin is installed / enabled).
I cannot figure out how to add my section inside Viewable Public Schema using Gql in plugin.
Anyone has any idea or snippet?
Related
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/)
I have followed every step given in the following repo GitHub - Adobe-Marketing-Cloud/aem-scf-sample-components-extension: Sample package for AEM Social Communities - Social
I have added the subtitle property to "com.adobe.cq.social.journal.client.endpoints.impl.JournalOperationsService" and created a page using the given template and tried to add the extended journal component and clicked on New Article and tried to enter some content and clicked on publish immediately. But after I click on Publish it's taking me to the same page and no content is being published. And I checked if the UGC is stored under /content/usergenerated/asi/jcr/content but no content is stored for the ectended Journal component.
Where as the other extended community components that are given in the above repo are are working fine. I have added the required client libraries. Can anyone help me what am I missing?
After a lot of research, I understood that when you are publishing a new blog article JS is not getting loaded.
Steps to resolve the issue:
1) Navigate to /etc/designs/acme/clientlibs/site
2) Delete the JS folder and js.txt
That's it you are good to go.
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.
I am developing a JIRA plugin and I'm trying to add a custom field to the Add project page. As far as I know, a custom field can be added only for an issue. Is it possible to add a custom field (a text field or a select list) at a project level?
I have found an plugin, which is able to add metadata on Project level.
Please take a glimpse at this link
Short answer: doable but not particularly easily
The way you do this is to write a WebWork plugin that changes the Java class that handles that webpage. The process is that the actions.xml file contains the AddProjects.jspa, e.g.
<action name="project.AddProject" alias="AddProject" roles-required="admin">
<view name="error">/secure/admin/views/addproject.jsp</view>
<view name="input">/secure/admin/views/addproject.jsp</view>
</action>
which tells you that the class name is AddProject, which you can extend to handle the user setting a value in this new field. Then you also need to decide how you're going to store values for each project (more info in the Practical JIRA Plugins or JIRA Development Cookbook books). The hardest part here is that the template files are .jsp files which you can't change directly with a plugin. What I usually do is write a ServletFilter to inject JavaScript to change the AddProjects page that way.
There is no elegant way, but you possibly can use Custom Project Properties for JIRA plugin.
This plugin allows to:
define list of custom fields for projects
define custom fields per project
fill custom fields on project administration page
I'd like to create a plugin that exports into a custom document format similar to the way that export to PDF and export to Word currently work in Confluence.
Does anyone have experience creating a custom export plugin for Confluence? If so do you know of any resources or samples that describe what would be involved?
Here are the most useful resources that I've found so far:
Plugin Tutorial - Adding a custom action to Confluence - This shows how to add an action to the "Tools" menu that appears at the top of a confluence page. Additionally it shows how to interact with the Page object to get more info about the page.
Plugin Module Types - The second guide I found helpful was the list of general plugin module types. It was informative to discover that a "plugin" is really a collection of "modules" and seeing this list was helpful to understand how to apply that model to creating a plugin of the type I was looking for. Additionally the Confluence Plugin Guide was also helpful for a breakdown on Confluence specific plugin modules.
The Confluence Developer FAQ - Useful for information on how to convert wiki content from a page into HTML as well as a number of other hard-to-find gems.
Finally, it was hard to find, but in order to understand how to "target" a particular menu or area of the existing UI to extend, I found it very helpful to read about the guide for Creating your Plugin Descriptor.