After a server crash, I had to re-install TYPO3 using my latest database backup.
While I was at it, I upgraded TYPO3 from whatever I installed about half a year ago to 4.7.2 and, consequently, also had to use a newer tt_news module (3.2.1).
Unfortunately, none of the news sections on my site show up now. All it says where they should be in the HTML code is:
<!-- CONTENT ELEMENT, uid:24/list [begin] -->
<div id="c24" class="csc-default">
<!-- Plugin inserted: [begin] -->
<!-- Plugin inserted: [end] -->
</div>
<!-- CONTENT ELEMENT, uid:24/list [end] -->
I did update the database when I installed the plugin and clicked the link for the updater script on the plugin's configuration page, although it didn't seem to do anything.
I'm really new to TYPO3, so I can't be sure it's nothing with the HTML template, which I had to reconstruct from scratch. Also, I'm not really sure yet how you would get an idea of what's going on (or wrong) in cases like this in TYPO3.
Please check the following:
tt_news static template is included or not.
Go through the extension manual and check whether the flexform options and typoscript configuration are correct.
Make sure that the typoscrpt object browser is error free.
Check the error log and set Install tool > All configuration > displayErrors = -1 for your IP address.
Related
yes, it's me with a further, maybe stupid question. I'm very new in TYPO3, I just started working with it. I know some programming languages but no typoscript. Therefore I'm working with the bootstrap package first.
I made some forms with TYPO3 core and so far everything was fine but there wasn't any possibility to customize the email (to sender). Therefore I first installed "Form: Mailtexts via plugin" but afterwards the form was not working anymore and I deleted it and everything was fine again.
After some research I have found powermail for creating forms with loads of cool functions.
So, I read four different tutorials about making forms in powermail and it's not working at all.
As far as I can evaluate the problem, I would guess that the last step is the problem, placing the content on the page.
After loading the page with the powermail elements an error message is shown
"TypoScript settings are missing. Did you include the related static templates? No form to show"
Of course I googled this error message and found this post https://github.com/derhansen/sf_event_mgt/issues/432.
In this post they include "fluid content elements" and "Event management and registration" extension and so did I. A new icon in the backend popped up "Events". Selecting this icon a further error message is shown:
"TypoScript settings missing Unable to find TypoScript settings for module. Please make sure, you have included the static TypoScript for the extension."
The page with the powermail elements is empty now, i.e. no more error message but it's also not working at all.
Please, does anyone understand what's going on here? I'm devastated :-(
Many thanks in advance for your kind help!
Best,
expikx
I tried to solve the problem by internet research and experiments
The plugin of powermail just informed you, that basic configuration is missing. The configuration is given via TypoScript and of course powermail brings some default configuration with it.
You now have to include them. You can do it by opening your default TypoScript template, change to the tab "Includes" and select "Main Template (powermail)". Save your template and reload your frontend.
I'm currently upgrading a TYPO3 v9 to v11. There I use the table content element in combination with tags. E.g. something like this:
Some Text with an <link https://domain.tld>external link</link>
In TYPO3 v9 I used this to get real links in the table:
<f:format.html parseFuncTSPath="lib.parseFunc">{cell}</f:format.html>
But in v11 the link is not parsed correctly. Output is:
<link https: domain.tld>external link
So the double slash and the closing </link> are gone.
I tried to use a custom parseFunc where I disabled htmlSanitize. Then the <link> tag stays intact, but isn't parsed at all.
Any ideas how I can get <link> work again? Or is there any other way to use links in the table content element?
<link> is old Syntax and migrated already in v8. However, this was still partly able in v9.
See: https://docs.typo3.org/c/typo3/cms-core/9.5/en-us/Changelog/9.0/Deprecation-83252-Link-tagSyntaxProcesssing.html?highlight=link
You should properly migrate your content to the new Syntax before upgrade. In v9 the corresponding UpgradeWizard should still be there, in v11 not.
From core side you cannot get it working again as core dropped this Syntax. Better migrate your content properly.
In TYPO3 7.6, when I exchange an image in the base language I am not able to add this image in an already existing translation record.
For example: I added image pic1.jpg in English (L=0), on translating to German (L=1) pic1.jpg is available for activation. Later I remove pic1.jpg and add pic2.jpg, probably clipping or otherwise modify the relation so I have data that I want to preserve.
I'm able to delete the German translation record and add a new translation in both list view and page->languages:"Add Translation" with new image(s) and all its modifications preserved, but that is a work-around loosing all translated fields in the process.
If my memory doesn't fail me, there was a dimmed FAL record appearing in the translation media tab once it was added in the base language back in former versions of TYPO3 (6.1).
Bug? Or am I missing something?
It's a TYPO3 v7.6 core bug which exists since 2014 but it was never fixed. See bug report: https://forge.typo3.org/issues/57272
There are multiple ways to solve this issue. I had this problem too and for me it only worked with the first solution.
1. Create a ViewHelper
It's a solution from Kai Tallafus who shared his ViewHelper in the comments of the bug report 57272 (see link to bug report above).
ViewHelper: https://forge.typo3.org/attachments/download/32333/FalTranslationFixViewHelper.php
Usage of the ViewHelper in Fluid Template:
<util:falTranslationFix record="{record}" tableName="tx_myext_domain_model_foo" relationFieldName="files" as="files">
<f:if condition="{files -> f:count()} > 0">
<f:for each="{files}" as="file">
{file.properties.title}
</f:for>
</f:if>
</util:falTranslationFix>
2. Install an Extension
I found two extensions who probably will fix the bug. I recommend the first one but it doesn't work for me but maybe it will for you.
repair_translation
faltranslation (only available on bitbucket -> bitbucket.org/t3easy_de/faltranslation/src)
3. Enable sys_language_uid field for the FAL Media
There is a workaround for the translation of the FAL Media in which you enable the sys_language_uid field. When enabled the enduser can select the language for the media element. This also not worked for me but I know from a friend that in one of his project it worked. Manual (in german): www.npostnik.de/typo3/workaround-fuer-uebersetztungen-der-datensaetze-mit-fal-media/
4. Update to TYPO3 v8 LTS
When you're working on a project which could be updated to the new Version, you should consider to make an update. The Bug is fixed in the TYPO3 v8 LTS.
The viewhelper won't work for the field media in tablep-pair pages/page_labnguage_overlay. (TYPO3 8.7)
You have to seperate your translateted parts in the fluid-template. The where-clause in the query should check for 'pid' instead of 'uid'. And you have to check for a relavant entry in the media-field of the $rawRecord.
I'm using Rich Text Editor with MiscTools plugin to edit text in CQ%
However when I open the HTML editor and create sth like this
<div id="test">Test <!-- Test Comment --></div>
the CQ rewrites it to after switch back to HTML mode and source edit mode
<div id="test">Test </div>
Is it possible to keep HTML comment tag <!-- --> in the source code?
Thank you for answer my question
I would suggest taking it out of the div and see if that works.
In CQ5.4-5.6.1 (not sure about latest version AEM6), the Rich Text Editor intentionally strips out all HTML comments. The only way to stop it from doing this is to modify the product javascript source code in WhitespaceProcessor.js. However, allowing HTML comments in this way wouldn't be recommended as it hasn't been fully tested it might cause other errors. If you still need this feature, then you might consider contacting Adobe Customer Care to request it to be officially added to the product.
I use Eclipse and I write jsp files with HTML5 content.
So I have for example this line:
<div class="test" data-role="test123">
In Eclipse I get the warning:
Undefined attribute name (data-role)
What needed to be done so these warnings won't appear anymore? In HTML5 this attribute is allowed (data-*) as you can see here: http://ejohn.org/blog/html-5-data-attributes/
It seems like Eclipse still has some problems validating HTML5 elements and attributes even now.
I'm running Mars 4.5.1 and I have had warnings about the <main> element, despite the fact that there are no warnings about the <section> element.
But there is a solution!
Window > Preferences > Web > HTML Files > Validation
Here you can tick the Ignore specified element names in validation checkbox and enter the names of any elements which Eclipse is incorrectly warning you about.
In your case, you will want to tick the Ignore specified attribute names in validation checkbox and enter the data-role attribute.
After you click 'Apply', Eclipse will ask you to do a full validation of the project. Select 'Yes' and the changes will take effect.
No more squiggly yellow lines YAY! :D
Your doctype
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
is for HTML 4.01.
data-* attributes were added in HTML 5. The doctype for HTML 5 is basically either
<!DOCTYPE html SYSTEM "about:legacy-compat">
or
<!DOCTYPE html>
Newer versions of Eclipse support HTML5 tags and the data-* attributes allowed in HTML5. However, when using the role attribute the proper syntax according to the ARIA Roles Model and XHTML Role Attribute Module is not to prefix the role attribute with data-* leaving just role and not data-role.
So <ul role="menubar"> is more correct than <ul data-role="menubar">. The validity of the syntax can be checked using the (X)HTML5 Validator. jQuery Mobile uses quite extensively the data-role attribute, though I'm not sure why.
Note: If you upgrade and you're still getting warnings on data-* attributes you may want to consider updating or removing any installed syntax-checkers such as JTidy. As of Indigo Service Release 1 the role attribute continues to trigger an undefined attribute warning in Eclipse by default.
I used this one with Aptana 3.6 when I'am coding AngularJS
Window > Preferences
I use the Aptana Studio plugin on Mac OS X; if I go Eclipse > Preferences > Aptana Studio > Validation > HTML, and create the filter *data-role* I no longer get this warning.
I believe on Windows it is Window > Preferences > Aptana Studio > Validation > HTML
Eclipse 3.6 introduced a new field under:
Validation -> HTML Syntax: Ignore specified attribute names in validation
Add the OpenGraph, RDFa or other non-HTML5 attributes you want the validator to ignore:
You will need to re-validate the project, then the warnings will be gone.
Eclipse observes the DOCTYPE declaration. In my case, the solution was using the code above at the first line of the files containing HTML code:
<!DOCTYPE html>
Related to that, there's this other question, already answered:
Why do we need DOCTYPE to the HTML/JSP pages?