Is there a way to set the default category for each entry in Movable Type. I am using Movable Type version 5.12
I could not find any method for it. Is there any way or a plugin to do this?
I think you should try the Default Categories plugin by Dan Wolfgang and see if it does what you need.
We've never implemented it for a customer, but Dan's an established developer with a good track record. I haven't heard of any problems with the plugin recently.
I've used Dan's 'Default Categories' plugin on both movable type v4.x and v5.x for a few media customers that needed to impose a specific category as default and I could confirm that the plugin works very well for both v4.x and v5.x.
Related
I look for a tutorial, help or an example that tells me what I have to do to write a grid element like 2-colums in basic typo3 (v9) with fluid but no other extension like gridelements, DCE, Templa Voila, etc. I want the same gridelements can do but I dont want to be depended to this extention and move it in my own site extention.
I tried the same with normal content elements (CE) like here:
https://docs.typo3.org/c/typo3/cms-fluid-styled-content/9.5/en-us/AddingYourOwnContentElements/Index.html
But how can I nest a CE in a CE? And how can I do this by drag&drop in the backend?
You can't. The page module doesn't support nesting
You can't nest CEs in a CE. On database level this would mean that you have to make a tt_content record a subrecord of a parent tt_content record. You run into several problems, basically the multilanguage support will be broken and the shortcut element does not function as you will expect it to. That is why the extensions "gridelements" and "mask" exist.
I integrated the gridelements configuration into my sitepackage. So I do not need to bother anymore with it.
Just for your info:
There is now an initiative that works on integrating this functionality into the core (Structured Content Initiative, https://typo3.org/article/a-structured-content-initiative/). Stay tuned to it.
There is nothing special about providing Gridelements via external files, since it's based on TSconfig, TypoScript and Fluid. That's why there is not that much about it in the documentation, since it's the same thing you would do with any other kind of sitepackage. The TSconfig and TypoScript parameters are already explained there, while the Fluid would be up to you anyway.
To have a kind of kickstarter just take any extensions providing Gridelements layouts as an example. A very popular one would be bootstrap_grids, which can be found in the TER or here: https://github.com/laxap/bootstrap_grids
You don't necessarily need the flexform controller of that extension, but the Configuration and Resources folders, show you how to configure stuff and you can see how that is included via ext_localconf.php
There are even comments i.e. in the TSconfig files to explain what is possible there and how to handle i.e. mixed environments with record and file based setups. Although it would be recommended to go for files.
You would at least have to add the necessary backend rendering methods to a draw item hook, that will modify the preview of the container element.
So basically you would have to rewrite everything that DCE, Flux, Gridelements or other similar extensions already do.
Which brings us to the question, why you want to avoid those extensions, since especially those three are well known, widely spread, well supported and available for currently supported TYPO3 versions.
I hope you can help me.
After upgrading the payone extension from 3.1.8 to the newest 3.5.5 and checking the correctness of payone configuration with its menu 'export configuration' I detect that the creditcard is not listed under the status mapping group though the mapping for it is set. But the credicard data itself is exported anyway under the clearingtypes. I reinstalled the extension, some times, but allways the same effect. There is also no log entry.
The creditcard is the clearing type I have ordered by payone, the other, which are listed under status_mapping not.
Here is the part of the .xml export.
<status_mapping> !!! no creditcard listet under status mapping!!!
<vor/>
<cod/>
<elv/>
<rec/>
<sb/>
<wlt/>
</status_mapping>
<payment_creditcard>
<min_validity_period></min_validity_period>
</payment_creditcard>
</global>
<clearingtypes>
<cc>
<title><![CDATA[Kreditkarte]]></title>
<id>3</id>
best regards
Christian
I marked that as a bug internally. However, I don't think this is a classic question for Stackoverflow. Feel free to add an issue at https://github.com/PAYONE-GmbH/magento-1 the next time something like this arises :)
I'll check whether I can pin down the issue and will get back to you.
Best,
Florian
Technical Partner Manager #Payone
I am in the process of localizing my application. Everything works well except one issue. According to the Apple docs, if you have a specific region, it should be selected first and then to the more general. So for instance, in my project, I have:
en.lproj
Localization.strings
en_US.lproj
Localization.strings
While I am set to US English in my settings, Monotouch is picking the en.lproj before en_US.lproj when it should be the other way around. Is this a bug or is this not supported?
Thanks,
Ray
Thanks, that link helped. And I re-read the docs and it does not work that way I thought on iOS, only OSX. So iOS only looks at locale only eg. en.lproj.
EDIT: might be fixed in latest Xcode 4.0.2 (just released) - I'm downloading this out now, and will re-edit once I've tested it.
Create two entities (call them "Manager" and "Employee", to stick with Apple's docs).
Create a relationship, "worksFor" from Manager (1) to Employee (many), and mark it as "not optional". (you'll probably need to create 2 relationships, mark 1 as inverse of other)
Hook up an interface using IB, according to Apple's original docs (NB: these don't work any more, but here's an almost exact recreation of the basic setup in Xcode4: http://rgprojection.blogspot.com/2011/04/xcode-4-and-core-data-macos-x.html) and use Bindings (as described in the linked post) to create/add/delete the objects.
Now try to save. ERROR: "worksFor is a required property".
In previous versions of Xcode, this worked as expected: you'd told Xcode that there was a bidirectional relationship, you told it that it was required, and so when it added the "Employee" to the "Manager", it automatically hooked-up the inverse.
Has anyone else worked out how to make Xcode4 do what it's supposed to? Is it an Xcode4 bug? I know that some of the CoreData support in Xcode4 has been deleted, with no replacement (yet), so I'm wondering if this has been deleted too?!
EDIT: here's another project, one I made from scratch, same problem. Although (xcode4 bug, definitely!) this time I created the Relationship in the "grid" editor view rather than the "tree graphical" view... and the generated source code for objects was different (should not be the case, obviously)
second project screenshot
EDIT2: StackOverflow was showing the screenshot above, but has now removed it, you'll have to click on the link. Sorry.
I haven't seen the problem you describe and I've created several data models under Xcode4. It appears to work just like it did in previous versions in that regard. I think you've got something else going on.
Xcode 4.0.2 seems to have fixed the problem - everything works as expected now, with no changes to code :)
Is there any way to enforce a template in Bugzilla to guide users fill in bugs descriptions ?
Actually, i'd like to put some markup texts in the bug description field and avoid the creation of custom fields.
I've installed version 3.2rc1.
Indeed, just check ../enter_bug.cgi?format=guided , which forms an example of the template feature. Half the work is already done for you.
The mechansism described under 6.2.5 Particular Templates (under the section called bug/create/create.html.tmpl and bug/create/comment.txt.tmpl) works pretty well for us. Even though you say you don't want to create custom fields, adding some arbitrary HTML is easy enough.