Dear Stackoverflow community,
i have a problem with the typo3 dce extension. I did not find anything from searching and have not seen this problem in any time.
When i create a field in the dce there should be a configuration in the textarea below the dropdown menu. (picture)
Empty DCE configuration
I can not create a working dce without this configuration.
I think it is a general problem but i do not know which one and from where it comes.
Any suggestions?
even if I dont work with DCE i got two possible solutions for you:
Looks like the extension requires silently fluid or css styled content included, so you can try to add them to your template (at the template configuration -> includes). Try "fluid_styled_content" first.
The second possible solution is a missconfiguration. Cause I dont know the structure i can just refer to the extension documentation -> User Manual
Related
Call me old fashioned, but there is nothing I can do but only to use the old version of Tiny MCE, which is 2.1.
So, what I'm trying to do is to add a "download" attribute to tag, after I open HTML editor I type this attribute, when saving it simply disappears. There is no official documentation to this old version on the official site. The new ones doesn't mention anything about this feature at all. overall editor look. code editor look
Also, I tried to add "download" in the extended valid elements configuration:
extended_valid_elements: "code[class|dir ,however no success as well.
Did anyone by any chance faced the same problem?
Could use a little bit of help.
Well, if anyone ever encounters the same problem, which I highly doubt, you would need to open tiny_mce.js file, and on the line 1928 there will be "A : "id|class|style|title|download" ", this is the place, where I added "download". Afterwards I was able to add this attribute in the HTML code editor.
im using a joomla template in my localhost. I would like to edit one of the on-screen module's position. i used chrome and firefox to inspect the elements and even changed the properties. it works the way i want, but the problem is, im not sure where these actual files are residing in my localhost. There are 100s of files and its frustrating there isn't an easy way to find out the exact file that i have to edit.
I understand that joomla contents are generated on the fly and thus it isn't easy to find the exact file. I have also seen some of the past related questions in stackoverflow.com, asked by desperate users like myself, nothing works.
Im hoping someone knows of a tool or a trick that can help me. I even tried indexing the localhost folder (c:\wamp\www\demo) to search file contents, it doesn't seem to work for some reason.
Pls help.
The position of the module is almost certainly determined only by the css in your template. Using web inspector in Firefox or Chrome you can see which file (and the file path) of any styles that are currently being applied to the module, so you can simply modify the rules in that files.
I love Mac
Since my files are in the localhost, i have been trying to search for the div class that is generated on the fly, but my pc couldn't thoroughly search the contents of the file.
On my mac, i searched for the div class word and hey! it showed me a list of files that contained the div class and i found the file in a matter of seconds! how cool is that!!
Thanks Guys, hope this helps someone too!
Im trying to locate certain javascript code in the codebase with no luck. This code appears in the head of every page. Note that it isnt a link to a file but certain code embedded in the head. I have tried the following ways but no luck
local.xml
head.phtml
page.phtml and all page templates
page.xml
Text search in codebase with keyword and
keyword '{variablename}'
Database search keyword '{variablename}'
but no results so far
Have a missed something? Any help would be really appreciated.
Thanks,
Loveleen
Assuming that the page templates still generally reflect the native Magento structure, if it's in the <head> of the page, then it can only be coming from one of three places:
The page template (1column.phtml, 3columns.phtml, etc.).
The <head> include file head.phtml.
An include of one of the first two.
I know you said you already looked in both of those places, but you can help narrow down the source by comparing what you can see in those locations with what you see in the generated page source. Is the analytics code you're trying to locate before or after something you can see in those template files?
Also make sure that you're looking in the template files of the correct theme.
Ok got it.. it was under System>Config>Design>Misc Scripts
i want to make a new joomla template, i dropped into that but i am confused now.
i want to know where is the joomla autogenerated css class list.
for example i insert a module in template and what is the css class for example for menu title or the css class for search input box or what is the default css class for readmore link in main.
i found a little in joomla doc but i want the whole list
I fail to understand how you are prepared to make a Joomla template which is far more complex than a plain CSS template, yet you are unable to find the necessary CSS files. You said you wanted to make a new template therefore shouldn't you know where you have put the CSS file?
You are in dire need of Firebug for starters. Have a look at all it's features. It will help you to find CSS files and the specific line you need to edit.
I assume you are editing someone elses template in which case this is the sort of location you will be looking for.
templates/you_template/css/file.css
It varies with different template so I suggest you download Firebug as I suggested above.
What is the best way to debug typoscript in the TYPO3 CMS?
Assuming I have a list, which is not displayed -
what is the strategy to look for the issue?
Debugging Typoscript is not the most comfortable task, but there are several possibilities. Here are the most common techniques:
Use the TS Object Browser in the backend: Choose the Web > Template module, then pick the page from the pagetree you need to debug. If there are any obvious syntax errors or redundant/missing brackets, an error message will be displayed. Switch between constants and setup and use the search field extensively. In your example, search for the myListview parameter if your TypoScript object is named myListview.
Use the Template Analyzer in the backend (also in Template module): It's similar to the Object Browser, but the Template Analyzer gives you valuable insights where in your setup the errors (or warnings) exactly are that have been spotted.
Outsource your Typoscript setup (+ constants) to files, then use a syntax highlighter in your favorite text editor. You get a better overview and the highlighting helps to avoid misspellings. For example:
PhpStorm TypoScript plugin (recommended combo)
Netbeans TypoScript plugin
Eclipse / Aptana: DEV3
Coda: ts4c
Textmate: Textmate Typoscript bundle
PSPad: sweeTS
jEdit: jEdit plugin
Sublime Text: Textmate Typoscript bundle
Activate the admin panel in the frontend and use the section "TypoScript". It shows you selected rendered (config) values, SQL queries, error messages and more. However, it's not complete and I'm not using it frequently so I am also keen on knowing more about it.
Wrap your Typoscript objects with the stdWrap.debugFunc Function or use the build-in debugItemConf method for all MENU objects. Debug output will be seen in the frontend. Read more in the TYPO3 Wiki
Most common errors (apart from typos) are wrong file paths, non-existing HTML-templates or missing subparts in modified templates. Also, forgetting to include static templates for an extension might leave the intermediate user puzzled. Just as a starting point :).
Hope that helps, please post any additions into the comments.
The most important thing is, not to rely on code you found via google. Have a look into TSref and check what is possible.
Just some little additions which are easy to overlook (IMHO):
The template analyser has an option: "View the complete TS Listing", so can search in the whole created typoscript! Including conditions.
TS Object Browser: you can check conditions to simulate different situations
If you need to debug TypoScript configuration in the backend, go to the "Info"-Modul, select a page in the page tree and then select "Page TSconfig" in the main window. There you will get a info about Page TS Config.
These system extensions are usually installed, but they can be deactivated:
tstemplate
tstemplate_ceditor
tstemplate_info
tstemplate_objbrowser
tstemplate_analyzer
info_pagetsconfig (info modul)
tsconfig_help (addition to the info modul)
It may happen, that someone else just deactivated them.
SIMPLE: use headerData in typoscript and view source code by this you can debug typoscript.