Is it possible to configure TYPO3 CMS to prevent it from expanding a media relation which is added to a page by default? Now each time a new media relation is added the detail view will be expanded.
I have checked the TSconfig docs and the install tool settings, but I did not find any related documentation or any similar question here on Stack Overflow.
As far as I can see from the code there is no possibility to do that.
The options Riccardo mentioned in the comment only work when opening a record with existing relations.
Your case (creating new relation) is handled via typo3/sysext/backend/Classes/Controller/FormInlineAjaxController.php
in combination with
web/typo3/sysext/backend/Resources/Public/JavaScript/jsfunc.inline.js -> inline.domAddNewRecord
there are no options to prevent expansion - only collapsing all other elements is possible (via expandSingle TCA configuration).
Related
This is a quick question for any experienced Django developers.
I have been trying to implement an admin page for 'Products' for an e-commerce store.
My vision for it was to have the top half of that form being used to enter information about a product which is a model I have defined. In the bottom part, I wanted to create some kind of inline to create ProductVariant (which is also a model I have) objects. Within the ProductVariant, I need some type of JavaScript behavior which displays or hides fields based on information entered at the Product section.
My question is would you recommend just completely throwing away the admin framework provided for that specific page and doing my own thing from scratch because I have just been struggling to get the custom functionality I want.
Yes to get the custom functionality you are describing, you’d probably need to implement, on your own, certain parts of the admin site (most likely overriding the templates). Some people even go as far as creating an entirely new admin site if they intend to work with frameworks like React.
That said, I’d look into the templates of the admin site in the Django libraries and, perhaps, copy most parts of the template then style and and add JavaScript as desired because you might miss certain key elements of the original if you do your own from scratch.
Problem
So we have quite a big project with lots of different Partial Views and a client side data binding framework (Knockout.js in our case).
One of the more problemtic parts is that is getting harder and harder to figure out which partial view is rendering an element that I see on my page.
So I need to debug this particular DIV. Okay, where do I find it?
Usually I try to find a very specific class or ID close by this element and do a search through the whole platform - far from ideal.
Question
So I was thinking about the following; tagging all elements (in debug mode) with the source file where they have been generated.
Right now I'm thinking about something like a precompiler that adds a data-source="" to every element. I might refer to an ID within a dictionary to prevent repeating all the long filenames.
Before I'm reinventing the wheel:
is there already something similar?
are there better alternatives?
We're using ASP.NET MVC, but any hints to how other platforms do this are perfect too.
If you are using Visual Studio, I highly recommend the Web Essentials extension. Among many great features, it has one called "Inspect Mode", part of the larger "Browser Link" feature, that does exactly what you are looking for; it identifies the file that a particular DOM element came from. It might be worth a shot if that option is open to you.
#Dirk, as per my understanding your issue is to easily identify the element/view. Adding data-source can be an option but before that have a look at this link
Editing Styles and DOM - Chrome Dev Tools
This page has many demonstrations which might be helpful to your problem. Furthermore, I do agree with Kevin suggestion.
I am working with wirecloud platform and I would like to know the following:
1.- Is is possible to resize the widget's width and height dinamically?
2.- Is it possible to fill a dashboard with widgets and ops dinamically?
Both questions aims to have a menu(widget) where users can click and change between different tabs.
Any help or idea would be highly appreciated.
EDIT 06/08/15
I am able to answer the second question: NO. As I can see in this request, the ability to add/remove widgets dinamically is not available, although is thought to be in future releases of the platform. Next question: when is it going to be available?
EDIT 13/08/15
I expected using:
MashupPlatform.widget.drawAttention();
could trigger a tab change, but no luck.
EDIT 27/08/15
Finally, we found a workaround. We take advantage of the iFrame property by which you can access to parent's document. From there, we are able to read the elements representing the tabs and generate their clicks at will.
Support for adding widgets and operators dynamically will be added on version 0.8.0, you can experiment with this feature if you install WireCloud from the develop branch on github. We are working on improving the documentation and polishing it for a new release at the end of September.
Although is great you find a work around using the iframe property for moving between tabs :), I recommend you to request the addition of such a feature using the WireCloud's issue tracker ;-).
P.D. MashupPlatform.widget.drawAttention(); need some fixes, but the idea is to provide some visual highlighting of widgets so user know there are updates in the widget. Something similar to the way google hangouts uses a green color for indicating the chat has new messages.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I found a web template on the net link and I want to allow end-users to edit the website using CMS. I found Orchad CMS, which is based on ASP.Net MVC. But the problem I'm facing is that I didn't find the full documentation on how I can map a web template similar to the one I provide to be managed inside a CMS such as Orchard so that end-users (non-technical users) can add new images, change the home page message, add new projects, etc.
This basically comes down to "writing a new theme" and implementing the functionality :).
The specific page you are referring to is fairly simple to implement in the Orchard which as a CMS, has extensive content definition and editing possibilities.
However you might want to try this first:
Forget about the template/theme for a second
Download and run Orchard in Visual Studio
Try to build your functionality with the default theme
Configure it so that other users (create a test user) can use it as you want (create new projects and change names/images).
To give you a head start for #3 (NO CODING REQUIRED):
Your functionality is a list of 'recent projects'
In Orchard, a 'recent project' can be implemented as a ContentType (of which users can 'create instances' also called ContentItem(s))
One way of defining contenttypes is by using the admin interface behind "Content Definition". Make sure the module "Content Types" is enabled.
Your 'recent project' contenttype basically has two properties namely "name/title" and an "image". These can be implemented in several ways which I won't all mention, but the easiest way is by adding Fields to the contenttype definition (A TextField for the name/title and an ImageField for the image).
tip: You can also implement the name/title by adding the TitlePart to the RecentProject contenttype instead of using a TextField. Parts are one of the concepts which make Orchard a very powerful CMS and this one is the easiest to understand. The result is more or less the same, you will get a way to add a title to the contentitem instances.
Up to this point you will basically be able to create "RecentProject" contentitems. You will now need to create a way to render your contentitems on the frontend. Again there are multiple ways of doing this. I'll continue on the path where you do not have to create any code.
Add a ContainablePart to your RecentProject contenttype.
Create a List named 'Recent projects' (optionally restrict the containable items to 'RecentProject' which should be listed after you add the containerpart to your contenttype
A list also has the AutoroutePart attached which is the mechanism for proving a frontend url to display contentitems. By default a url is created based on your title to this would result in a page /recent-projects
Make sure the Lists module is enabled
Read carefully: Do not create your RecentProject contentitems using the link in the upperleft of the admin ("New > RecentProject"), but go to your 'Recent projects' list which you just created. There is an option to create new items in that specific list which automatically hooks up the items to the list (this is all done using the ContainerPart).
At this point you can go to /recent-projects and see your Recent Projects list being displayed in Detail mode. The Detail display of a List basically renders each of its Contained items in Summary mode (and also a optional pager). Don't mind the way it looks right now. If you got everything up to here then you can start with the first link I mentioned about writing a new theme, but more importantly you should try to understand "Accessing and rendering shapes" and "Understanding placement info" both of which are used to manage those display modes like "Detail" and "Summary".
Enable the Shape Tracing module to help you with this. It is gold!
The reason I am keen to do this is that we have a wiki which works great, but I would like to store help pages for an internal application in the wiki and link to those pages direct from the app. Although we wouldn't have concerns with people seeing the non-article stuff (i.e. the help pages) when viewing the pages from the rest of the wiki, for it to be streamlined when viewed from the application I thought it would be ideal if I gave it a simplified skin which I would design.
I have already found out that URLs can have the useskin= added (e.g. as is done in the Preview Skin page within the User Preferences pages), but following the links will revert you to your normal chosen skin.
Is there perhaps some way to adjust the skin, so that all the links contain useskin=? (I think this might have issues, since you appear to need the full pagename for useskin to work (e.g. ..../w/index.php?title=blah....&useskin=cologneblue as opposed to the short URLs).
If this isn't a smart way to go, I could consider different approaches (I run the box the wiki is on and could create a distinct wiki perhaps, although there might be disadvantages to this, such as needing to combine the user tables and maybe this would still pick up the user's preferred skin unless I re-coded things).
Any sensible suggestions gratefully received! Let me know if there's any more info you might need or if I need to clarify any points about my objective.
[I did submit this on the MediaWiki.org Support Desk page, but it got no response... I hope my question isn't that bad!!]
You could put all your content in its own namespace, then set the skin for that namespace using this extension (I've used it, it works well enough):
http://www.mediawiki.org/wiki/Extension:SkinPerNamespace
If you don't want to lock them all into a single namespace, you can also use the SkinPerPage extension to mark the pages individually.
Why not change the default skin to the skin you want?