Questions around the TYPO3 integration and plugins as well as Flow and NeosCMS
Forum rules: Always add your TYPO3/Flow, Aimeos and PHP version as well as your environment (Linux/Mac/Win)
#2299 by Alexander
31 Dec 2015, 15:49
aimeos wrote:Well, you can paste the code into the input field. It doesn't display nicely but it should work even if the TYPO3 Extbase command controller doesn't offer text area fields.

It's true, I can paste the code, but execution is not working. After execution I'm getting an error message telling that the task "Extbase-CommandController-Task (extbase)" didn't succeed. Without the TypoScirpt it succeeds.

aimeos wrote:
Alexander wrote:By the way: There's an interesting difference between the two methods sending e-mails. Sending with Extbase gives a nice HTML-mail but the Aimeos task does not - almost all of the formatting except line breaks is not visible at least in Thunderbird. That's why I wanted to use simple text.


Then you didn't enter a valid path to the theme files. The Extbase command controller uses "typo3conf/ext/aimeos/Resources/Public/Themes/elegance" by default. We added some code that this will be also set by default in the e-mail scheduler in the future.

There is exactly the same value "typo3conf/ext/aimeos/Resources/Public/Themes/elegance" as default in the "Aimeos Shop E-Mails"-task. Nevertheless the html-formatting is not working as using Extbase. But that's OK for me.

aimeos wrote:The problem with the missing e-mail translation was a misnamed variable. We've fixed that in the git repository and it will be part of the next minor release.

Thank you very much for all your endeavor!
#2300 by aimeos
31 Dec 2015, 16:06
Alexander wrote:It's true, I can paste the code, but execution is not working. After execution I'm getting an error message telling that the task "Extbase-CommandController-Task (extbase)" didn't succeed. Without the TypoScirpt it succeeds.


Good to know!

Alexander wrote:There is exactly the same value "typo3conf/ext/aimeos/Resources/Public/Themes/elegance" as default in the "Aimeos Shop E-Mails"-task. Nevertheless the html-formatting is not working as using Extbase. But that's OK for me.


You could try using an absolute path. That should always work.
#2303 by Alexander
02 Jan 2016, 14:15
aimeos wrote:
Alexander wrote:There is exactly the same value "typo3conf/ext/aimeos/Resources/Public/Themes/elegance" as default in the "Aimeos Shop E-Mails"-task. Nevertheless the html-formatting is not working as using Extbase. But that's OK for me.


You could try using an absolute path. That should always work.

Yes, it does (to other readers: local path on the server, not the url). Thank you!
#2310 by Alexander
06 Jan 2016, 20:56
aimeos wrote:
Alexander wrote:There's also a bit strange problem with sending e-mails, but I don't know if this has to do with Aimeos: As long as there are no e-mails to send, the task for sending e-mails is executed every minute (in planned tasks, the date/time-stamps are updated correctly), but as soon as there is actually an e-mail to send, no e-mail is being sent and "last execution" does not update anymore and "next execution" gets an "-". Manual execution of the task works, and the e-mail is being sent.


Are there any error messages in the log (admin interface, first tab, second panel) resp. in the madmin_log table?

This problem disappeared, but I didn't know why. The reason was, that I changed from html+text emails to text only e-mails.
Executing "/usr/bin/php /var/www/html/typo3/cli_dispatch.phpsh scheduler" in the shell results in this error message while creation of the html part of payment e-mails:
PHP Fatal error: Call to a member function typoLink_URL() on a non-object in /var/www/typo3_src-7.6.0/typo3/sysext/extbase/Classes/Mvc/Web/Routing/UriBuilder.php on line 705
<div class="common-summary-detail container">
<div class="header">
<h2>Details</h2>
</div>
<div class="basket">
<table>
<thead>
<tr>
<th class="details"></th>
<th class="quantity">Anzahl</th>
<th class="unitprice">Preis</th>
<th class="price">Summe</th>
</tr>
</thead>
<tbody>
<tr class="product ">
<td class="details">
<img src="http://_DOMAIN_/fileadmin/PATH/IMAGE.jpg" />
<a class="product-name" href="

I think, that means, Aimeos isn't able to create that link if the scheduler is executed by the command "...cli_dispatch.phpsh scheduler". Manual execution of the task from within TYPO3 backend leads to no error, and the pageid is configured.
Is there a simple solution? If not, I will again disable html.
#2311 by aimeos
06 Jan 2016, 22:45
Alexander wrote:This problem disappeared, but I didn't know why. The reason was, that I changed from html+text emails to text only e-mails.
Executing "/usr/bin/php /var/www/html/typo3/cli_dispatch.phpsh scheduler" in the shell results in this error message while creation of the html part of payment e-mails:
Code: Select allPHP Fatal error:  Call to a member function typoLink_URL() on a non-object in /var/www/typo3_src-7.6.0/typo3/sysext/extbase/Classes/Mvc/Web/Routing/UriBuilder.php on line 705



Seems like it's impossible to create FE URLs in scheduler tasks due to a bug in TYPO3:
https://forge.typo3.org/issues/67355

The only possibility is to use the Extbase scheduler task which creates an working environment. We will remove creating links in the standard e-mail scheduler task in the next minor release so generating HTML e-mails won't throw an exception.
#2333 by Alexander
16 Jan 2016, 13:28
Translation by TypoScript is working now in the scheduler tasks. Thank you!
But it doesn't seem to work in the template TypoScript. I am trying to translate attribute values because there's no language selection combobox in the Aimeos backend, but nothing happens. The same is true for the attribute names, so I am using the default "Option"-attribute as the category of the values. This is my TypoScript:
plugin.tx_aimeos.settings.i18n.en.0 {
domain = client/html
string = german attribute value as in the database
trans = english attribute value
}

Is it possible to make such a translation?

aimeos wrote:Seems like it's impossible to create FE URLs in scheduler tasks due to a bug in TYPO3:
https://forge.typo3.org/issues/67355

...We will remove creating links in the standard e-mail scheduler task in the next minor release so generating HTML e-mails won't throw an exception.

The task is no longer blocking, but unfortunately there's still a problem: Now, the html of the e-mails still contains the <a>-tag, but with an empty href.
<a class="product-name" href="">PRODUCTNAME</a>

That means, there's a link shown in the e-mail with no URL.

Thanks and best regards
#2334 by aimeos
16 Jan 2016, 15:33
Alexander wrote:I am trying to translate attribute values because there's no language selection combobox in the Aimeos backend, but nothing happens. The same is true for the attribute names


Attribute type names (e.g. "color", "width", etc.) are translatable by their codes:
https://github.com/aimeos/aimeos-core/blob/2015.10/client/html/layouts/catalog/filter/attribute-body-default.html#L78

For attribute options (e.g. "white", "black", etc.) names for different languages can be associated in the admin interface.

Alexander wrote:The task is no longer blocking, but unfortunately there's still a problem: Now, the html of the e-mails still contains the <a>-tag, but with an empty href.
<a class="product-name" href="">PRODUCTNAME</a>

That means, there's a link shown in the e-mail with no URL.


We don't work with if/else here but use an URL view helper that produces no links at all, so this is a side effect. The empty "href" in the link tag should be no problem. If you don't like the mouse cursor to change to a pointer, you can fix that in the CSS for the e-mails.
#2335 by Alexander
16 Jan 2016, 18:40
aimeos wrote:For attribute options (e.g. "white", "black", etc.) names for different languages can be associated in the admin interface.

For other types of texts there's a language selection combobox in the admin interface, but I can't find one for attribute options. I am configuring these in the admin interface->product->attribute and am adding them at the right side. There are only the fields (in German): Status, Typ, Schlüssel, Bezeichnung and Position des Eintrags für den selben Typ. There's also no langid field in the table mshop_attribute.
Where exactly can this be configured?
#2338 by aimeos
17 Jan 2016, 11:39
Alexander wrote:I am configuring these in the admin interface->product->attribute and am adding them at the right side. There are only the fields (in German): Status, Typ, Schlüssel, Bezeichnung and Position des Eintrags für den selben Typ. There's also no langid field in the table mshop_attribute.


There's a tab "Text" in the attribute item panel where you can add attribute names in different languages.