Beeing new to Typo3, I've just installed jfmulticontent, but obvisouly, there's more to it than simply importing and installing. The documentation that comes with it on the other hand seems to be nice for people, who already know what they are doing. Does anybody know, where I can find some beginner-friendly installation-instructions and general documentation about that plugin?
Be sure you import the static files of the extension.
After installing the extension, you have to add the static “Multi
content (jfmulticontent)” to your template
I don't know your site structure. Try click on template, then click on your site root. Choose Info/Modify from toolbar and then click on Edit the whole template record, Includes.
Extension manual: http://typo3.org/extension-manuals/jfmulticontent/2.7.3/view/toc/0/
Try to be more specific regarding your problem. This way we can help you much better.
Related
I currently got the task to upgrade a custom made CRM extension named "kbs". It was developed on TYPO3 4.7 and using old namespaces in its classes like "Tx_Kbs_Service_TestService" etc.
I want to upgrade this whole extension to be able to work properly with our current backend version of 6.2. More specifically i want to be able to use the extension builder to make changes to this extension which i am currently not able to do on the 6.2 TYPO3 backend. It is not even an option to select the "kbs" extension in the extension builder.
Of course i reasearched the web but I find it very difficult to find information what you have to do in order to addapt a custom extension.
So far I assume that i will have to change all the namespaces in all my classes manually and maybe watch out for decrecated classes. But I do not really know if that is the way to go.
Does anyone have and guidelines, links or tipps for me? I would really appreciate it!
Thanks in advance,
Simon
To the first question:
In extension_builder only extensions are changeable, they had their original configuration made by extension_builder.
Extension builder itself is only an option to use, and there were also other options to kickstart an extension.
Update:
This is true, that extension builder is not an "editor" for extensions but a tool to help kickstarting an extension.
If I would get the task and extension_builder would be available I would not use it to make changes on the code. It is not 100% sure, that manually changes were not made on the code after its last automatically generated version. And if dummy actions were changed and properly excluded from the config they could be also deleted.
I think your best choice to change the things manually.
There are two source to read first:
TYPO3 6.2 Release Notes.
What's new presentation (TYPO3 6.2)
They contains breaking changes and some example.
If you do not change the PHP version, than changing the Namespaces and some deprecated functions. (The sources above could help to get an idea on those)
One tricky part could be to migrate old image logic into the "new" FAL (File Abstraction Layer). If you don't need to deal with images, then it must be an easier thing to go with.
There is also an extension to help with some migration stuff: smoothmigration.
You can find some hints in this presentation also:
jweiland: Smooth Migration TYPO3 4.5 > 6.2 LTS
Within Selenium IDE for Firefox, under Options -> C# / NUnit / Webdriver, there is a button 'Source' to view the conversion formatter.
It is displayed in read-only format.
Is it possible to get access to this file in order to customise the export process?
Sorry if this seems like a trivial question, I've found plenty of people complaining about not being able to perform various tasks online and a few responses that indicate that custom export is supported, but I can't seem to find a way to access the file to perform the work.
Thanks
I think I found a solution to this problem.
Though you can't customize any of the built in exports, like C# / NUnit / Webdriver, you can create a completely new exporter. I'd recommend modifying an excising one.
Get the source exporter you would like to modify. Ex Options->Options->Formats->C#/NUnit/Webdriver->Source. And copy it to a text editor.
Edit this code.
Options->Options->Formats->Add(button) and paste your new exporter.
I think you have to copy and paste the text, there is not file upload.
This worked for Selenium IDE 2.5.0
Hope this helps!
EDIT: In addition to my answer above, it may be easier to just write your own parser for the Source of your IDE Test.
The source is read-only because it has been provided by a Selenium IDE Plugin.
The source is usually helpful if you want to make a very simple formatter. Usually a better way is to create your own customised version of the formatter and package it in a plugin. Take a look at the source itself and the plugin tutorial at http://docs.seleniumhq.org/projects/ide/plugins.jsp
You can find some more information and slides about Selenium IDE plugins on my blog.
Cheers,
Samit Badle
Selenium IDE Maintainer. Twitter: #samitbadle
Blog: http://blog.reallysimplethoughts.com/
Should be pretty simple. I am trying to find what theme is being loaded in Magento to create my own custom theme. The problem is the mine (ver. 1.7.0.2) has no files in the frontend->default->default folder so I can't put any print statements there or see which template Magento is loading to learn more about it. Print statements in base->default don't seem to work either.
And where is the home page template located?
I don't know why Magento makes this so hard or maybe I'm just looking at old info that's not applicable anymore.
Turn on template path hints. Also disable the cache from System > Cache Management while you are doing any theme work.
+1 for other answer suggesting you turn on template path hints. That is a great way to figure out the structure of how things work in Magento.
I would also recommend the user guide. It's been updated to apply to 1.7. You used to have to pay for the guide but they make it available for free now.
http://www.magentocommerce.com/resources/magento-user-guide
As well as the latest designers guide that has info specific for templates etc.
http://www.magentocommerce.com/design_guide
what files do i need to modify / add if i want to add another frontend plugin (pi) to a TYPO3 extension? this should be done by hand and not with the kickstarter...
The best way to learn the answer to this question, is to make another plugin like the secondary one you want to add, and then try to merge the two manually. The answer to the question is dependant on what your secondary plugin does.
[Rest of explaination removed, as it struck me that someone must have answered this before. Googling "typo3 add plugin" reveals Ingo Renner's Adding a new plugin to an existing extension on the first page. Please do a little research before asking!]
I use javadoc to document my classes and methods. I would like to add some overview information to my packages, too. I like how Eclipse creates a stub of a matching Doc Comment for each class or method once I type /**<Enter>. Does Eclipse have an easy way to generate a package.html file, too?
Update 4 years later (Oct. 2013)
javabeangrinder's answer (upvoted) mentions the following trick:
To create a package-info.java file in an existing package:
Right click on the package where you want a package-info.java.
Select new->package.
Check the Create package.info.java check box.
Click on Finish
Original answer (May 2009)
There is no template or wizard to easily create a package.html file.
As mmyers said in his comment, since Java1.5, the correct file to create would be package-info.java.
That file can be used not only for javadocs, but also for package-level annotations (as illustrated here).
There is an opened Bug (#86168) for demanding a wizard for the creation of package-info.java (since the class wizard does not allow the package-info name).
The reflections on that topic are on since... 2005! The problem is that any solution should
be implemented in a way that it also helps with 1.4 code.
The current workaround is to create a package-info.java as a text file.
From that point forward, package-info.java behaves as a normal Java class, and Eclipse places a package-info.class file in the output folder.
The Javadocs are correctly built using package-info.java, and not the package.html file.
(source: developpez.com)
Note (in response to Strawberry's comment):
bug 77451 (2004!, for package.html)
bug 163633 and bug 163926 (2006, for package-info.java)
both wish a preview of the package overview in package-info.java in the Javadoc
view.
So far, no patch has been proposed/implemented.
There is simply not enough demands for that feature to be added.
In eclipse
Since package-info.java isn't a valid identifier for a class it cannot be created as a class in Eclipse.
I found that when you create a new package there is a check box to check if you want a package-info.java.
To create a package-info.java file in an existing package:
Right click on the package where you want a package-info.java.
Select new->package.
Check the Create package.info.java check box.
Click on Finish
The JAutodoc plugin does a great job of this, as well as all your other documentation needs. Install and configure the plugin and right click the package and click JAutodoc > Add Package Javadoc
There are configurations and templates available for the .java or .html package documentation.
This plugin also does a great job of standardizing all your Javadoc needs, with a great deal of customization.
http://jautodoc.sourceforge.net/
There's a plugin that seems to create package.html files. I haven't used it but someone landing here might find it useful.
http://sourceforge.net/projects/package-javadoc/