Giter VIP home page Giter VIP logo

in2code-de / powermail Goto Github PK

View Code? Open in Web Editor NEW
85.0 17.0 162.0 32.71 MB

This is the official repository of the TYPO3 extension powermail! Powermail is a well-known, editor-friendly, powerful and easy mailform extension for TYPO3

Home Page: https://in2code.de

PHP 71.45% JavaScript 3.05% HTML 8.87% Gherkin 6.98% Shell 0.10% SCSS 9.55%
powermail typo3 typo3-cms-extension form mailform-extension

powermail's Introduction

TYPO3 Extension powermail

Powermail is a well-known, editor-friendly, powerful and easy to use mailform extension for TYPO3 with a lots of features (spam prevention, marketing information, optin, ajax submit, diagram analysis, etc...)

⚠️ TYPO3 13 compatibility
See EAP page (DE) or EAP page (EN) for more information how to get access to a TYPO3 13 version

⚠️ Deprecations, planned breaking changes for V13 and features

Double OptIn and TypoScript setting "Do not save to DB"

This combination will not work anymore in V13. If the person responsible for data security desides not to save anything into the database, no data may be saved to the database, even not in the double opt-in process.

If you need this earlier than the next major (public) release, please contact us for the extension EXT:powermail_cleaner. With this extension it is possible to set that for each plugin individually.

Plugins / content elements pi2 - pi4

The content elements for frontend editing will be moved to a separate paid extension.

Future: Powermail Powerpack

Next to extensions EXT:powermail_cleaner, EXT:powermail_ratelimiter and the frontend editing stuff, there will be another paid extension EXT:powermail_powerpack. This extension will contain additional features, we developed throughout the last years and want to make available to the broader public, for example:

  • use an email address only once per plugins
  • maximum "seats" per plugin (like a very, very basic registration)
  • ...

1. Documentation overview

2. Installation

Quick guide:

  • Just install this extension - e.g. composer require in2code/powermail
  • Add a static typoscript template to your root template
  • Add a new form (with one or more pages and with some fields to a page or a folder)
  • Add a new pagecontent (plugin) with type "powermail" and choose the former saved form
  • That's all, you can view the result in the frontend

3. Administration corner

3.1. Versions and Support

Powermail TYPO3 PHP Support/Development
12.x 12.x 8.1 - 8.2 Features, Bugfixes, Security Updates
11.x 12.x 8.1 - 8.2 Support dropped
10.x 11.x 7.4 - 8.1 Bugfixes, Security Updates
9.x 11.x 7.4 Support dropped
8.x 10.x 7.2 - 7.4 Security Updates (paid backports are possible)
7.x 8.7 - 9.x 7.0 - 7.4 Security Updates (paid backports are possible)
6.x 8.7 - 9.x 7.0 - 7.x Support dropped
5.x 8.7 - 9.x 7.0 - 7.x Support dropped
4.x 7.6 - 8.7 5.5 - 7.2 Security Updates (paid backports are possible)
3.x 7.6 - 8.7 5.5 - 7.2 Support dropped
2.18 - 2.25 6.2 - 7.6 5.5 - 7.0 Support dropped
2.2 - 2.17 6.2 - 7.6 5.3 - 7.0 Support dropped

Do you need free support? There is a kind TYPO3 community that could help you. You can ask questions at https://stackoverflow.com and tag your question with TYPO3 and Powermail. In addition there is a slack channel in the TYPO3 slack ext-powermail.

3.2. Changelog

Please look into the changelog of powermail

3.3. Suggested Extensions for powermail

  • email2powermail Automatically convert emails to a link to a powermail form Link
  • powermailrecaptcha Google recaptcha Link
  • invisiblerecaptcha Google invisible recaptcha Link
  • powermailextended Is just an example extension how to extend powermail with new fields or use signals Link
  • powermail_cond Add conditions (via AJAX) to powermail forms for fields and pages Link
  • powermail_fastexport Extend powermail for faster export to .xlsx / .csv files. This is useful if you have many records to be exported. Link

3.4. Product Owner

The product owner and author of the extension is Alex Kellner from in2code. Beside that every in2code colleague is allowed to support further development if she/he wants. In addition there are a lot of other contributors that helped to improve the extension with their Pull Requests - thank you for that!

3.5. Release Management

Powermail uses semantic versioning which basically means for you, that

  • bugfix updates (e.g. 1.0.0 => 1.0.1) just includes small bugfixes or security relevant stuff without breaking changes.
  • minor updates (e.g. 1.0.0 => 1.1.0) includes new features and smaller tasks without breaking changes.
  • major updates (e.g. 1.0.0 => 2.0.0) normally includes basic refactoring, new features and also breaking changes.

We try to mark breaking changes in the changelog with a leading !!! and try to explain what to do on an upgrade (e.g. VieHelper name changed from vh:foo to vh:bar in templates).

In addition powermail is using Git Flow as Git workflow. That means that there is one branch which contains new and untested code: develop. The branch master only contains tested code which will also be tagged from time to time.

Based on release early, release often we try to release new versions as often as possible into TER and to github/packagist.

3.6. Automatic Testing

Behaviour tests

There is a huge testparcours that have to be passed before every release. For example there is an automatic test where the browser tries to submit 18 different strings and numbers to a field that accepts only phone numbers to test serverside validation. After that the same process is done for clientside valiation. There are also some smaller tests like "Is it possible to submit a form on a page where two different forms are stored?".

See readme.md for some more information about behat and selenium tests on powermail.

Unit tests

At the moment powermail offers 543 (and growing) unit tests that have to be passed before every release. See more information about unit tests or code coverage in powermail in the readme.md

3.7. Code quality

Beside respecting PSR-2 and TYPO3 coding guidelines, it's very important for the project to leave a file cleaner as before. Especially because it's a really large extension with a lot of functionality and a history of 10 years (!) and of course some technical debts, that have to be fixed step by step (e.g. moving logic completely to Domain folder, ...). Look at Sonarqube for some interesting details on that.

3.8. Contribution

Pull requests are welcome in general! Nevertheless please don't forget to add a description to your pull requests. This is very helpful to understand what kind of issue the PR is going to solve.

  • Bugfixes: Please describe what kind of bug your fix solve and give us feedback how to reproduce the issue. We're going to accept only bugfixes if I can reproduce the issue.
  • Features: Not every feature is relevant for the bulk of powermail users. In addition: We don't want to make powermail even more complicated in usability for an edge case feature. Please discuss a new feature before.

3.9. Development

Compile and minify (uglify) JavaScript, compress CSS:

$ cd Resources/Private
$ npm install
$ ./node_modules/.bin/gulp

4. Screenshots

4.1. Example form with bootstrap classes:

Example form

4.2. Backend module mail list:

Backend Module

4.3. Backend module reporting:

Backend Module2

powermail's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

powermail's Issues

{f:cObject(typoscriptObjectPath:'lib.receiver')} including userFunc does not return content in receiver-field

I have a Receiver TS-cObject as

{f:cObject(typoscriptObjectPath:'lib.receiver')}

The lib.receiver is a userFunc which return one or more E-Mail-Adresses in response to some conditions.

If I look at page.5 < lib.receiver as test, I see the response. But the Receiver-Address in the Email is always empty, thus no Mails are generated.

If i fill the lib.receiver with text like [email protected], everything works as expected.

Seems the Class gets not loaded in this context.
Tried namespace loading as well as includeLibs TS, both don't work.
Tried on different installations as well.

Can anyone confirm?

List View: Uncaught TYPO3 Exception: NAMEPREP: Prohibited input U+00000026 [Typo3 8 LTS]

On Typo3 8 LTS when I click on List View and there's a powermail plugin (Content Element) in the page I get this error:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: NAMEPREP: Prohibited input U+00000026 | InvalidArgumentException thrown in file /var/www/typo3_src-8.7.1/vendor/mso/idna-convert/src/Punycode.php in line 335.

If I delete the powermail plugin from the page and click on List View again, the error goes away and I can then see the responses stored in the page.

Tested in several pages and the only way to have the List View working is deleting the powermail plugin from the page.

I linked the complete exception output just in case. It seems to be a problem with parsing of the powermail Flexform.

I'm under a development subdomain. E.g.: dev.mydomain.com
Powermail version: 3.17.0

PS: Powermail is an excellent extension! Thanks for looking into this.

Typo3 Exception.html

[globalString = GP:tx_powermail_pi1|field|anschaffungsvorschlag_fach = Allgemeines] didn't work

[globalString = GP:tx_powermail_pi1|field|anschaffungsvorschlag_fach = Allgemeines]
lib.anschaff_mail = TEXT
lib.anschaff_mail.value = [email protected]
lib.anschaff_fach_name = TEXT
lib.anschaff_fach_name.value = Fachreferat Allgemeines
[global]

If i set the options without
[globalString = GP:tx_powermail_pi1|field|anschaffungsvorschlag_fach = Allgemeines]
the mails will send, but with this option i get no mails.

With this statement i will change mail-Adresses and subject in the mail if the field "anschaffungsvorschlag_fach" has diffrent subjects.

I have no idea whats wrong? I find this example on other sides as well.
Have someone any help?

Bernd

Mail layout styling

Hello

Is there any way to style the overall template sent by emails? I'm talking about the Mail.html file in the "Layouts" folder. How would one go about adding inline images (think logo, header, etc) that would be sent along with the text supplied in the bodytext?

I don't think I've seen this explained in the docs so I was wondering if it was possible at all. I could link them to an external domain no problem, I was just wondering if inline attachments are a possibility, maybe with some of your viewhelpers?

Thank you

lib.parseFunc_powermail is empty because of wrong loading order

lib.parseFunc_powermail is set in ext_typoscript_setup.txt. My understanding is that stuff in this file is by default loaded BEFORE stuff from static templates like fluid_styled_content. This has the effect that
lib.parseFunc_powermail < lib.parseFunc_RTE
does not work, because lib.parseFunc_RTE is empty at this point.
This results in wrong or missing formatting in sent mails.
I think we use the default settings in our project, so this should be relevant to most installations, independant of TYPO3 version.
You can check if you suffer the same problem in every specific installation via the Template Module in TypoScript-Object-Browser or Template Analyse.

We solved this issue by dupicating
lib.parseFunc_powermail < lib.parseFunc_RTE lib.parseFunc_powermail.tags.link.typolink.forceAbsoluteUrl = 1
into our project TypoScript, which is loaded after all other TypoScript was loaded.

export to csv file

I would like to export the mails to a csv file. But this file is empty. I have tried the planner and the backend module. The export to xls file runs correctly.
I use the default templates and partials.
TYPO3 8.7.1 / powermail 3.19.0

[Feature] Duplicate and/or Copy-Button

Sometime when powermail is used for bigger forms, it would be advantagous to be able to copy/duplicate fields. Sometimes there are questionaires with same answer options, or input with similar spec's.

A button like the "Add new record" button on the right, e.g. "Duplicate record" would do the job.

The main advantage would be the option to edit the fields in bulk in the list view (as the associations are untouched.

"Numbers Only" validation fails to validate zip codes "01234"

German postal codes consist of digits only, 5 of them. They may start with a zero 0.

We wanted to use the "numbers only" field validator to verify that the user only inputs digits, but that fails with zip codes like 01234.

This is because StringValidator::validateNumbersOnly() converts the input to int, which strips off the leading zero. You could instead use is_numeric.

problems with SSL/https and the form action url

Hi,

thanks for this very useful and comprehensive form extension. We are using ssl https on our website. Problem is that the powermail url ist http which causes an error and is of course not wanted. Is there something in the config I missed? Some solutions are telling to alter templates. But is there no other way to fix this problem? Thx!

Florian

Wrong mail text parsing if static template files from extensions include before all static templates

TYPO3 v7.6.15 and powermail 3.11.2

My typoscript is include static from custom extension. To avoid problems with some system extensions (felogin ...) the option "Static Template Files from TYPO3 Extensions" is set to "Include before all static templates if root flag is set".

My powermail receiver mail textfields contain paragraphs.
With the above configuration, p tags are removed in sent and stored mails.

I temporary fixed this issue, by adding the lib.parseFunc_powermail < lib.parseFunc_RTE setup from powermails ext_typoscript_setup.txt to my powermail typoscript setup file.

Manipulate export values

Hey,

is it possible, to manipulate the export / answer values too?

sort of:

manipulateVariablesInPowermailAllMarker {
  export {
    …
  }
}

Many thx in advance,
Martin

Marker is set incorrectly on translated fields

On our TYPO3 8.6, we face the problem, that every time, we add or update a translated field, the marker of the translated fields is set to the translated title - the marker from the original language gets overriden.

Example:

  • original field name "Firstname" -> marker name "firstname"
  • adding translation "Vorname" -> marker name (in translated field): "vorname"

This leads to incorrect frontend markup. All labels are translated correctly.
We checked all language settings and tested different language settings - no success at all.

TYPO3 Version: 8.6
PHP Version 7.0.13

Additional field type not shown for newly created field

I defined my own field type via PageTSConfig:

tx_powermail.flexForm.type.addFieldOptions.test = Testelement

Now I create a new form field within a form page, using the "new record after this record" button.
My custom type is not available.

Only after saving this once, the additional type is selectable in the type dropdown.

2017-01-26 powermail custom type

Use of captcha with Typo3 8.2

Hi,

When adding a captcha field to a form with a typo3 8.2 installation, the following error message shows on the frontend:
Uncaught TYPO3 Exception
#1256475113: The argument "field" was registered with type "In2code\Powermail\Domain\Model\Field", but is of type "string" in view helper "In2code\Powermail\ViewHelpers\Validation\ErrorClassViewHelper". (More information)

InvalidArgumentException thrown in file
/Applications/MAMP/typo3_src-8.2.1/vendor/typo3fluid/fluid/src/Core/ViewHelper/AbstractViewHelper.php in line 318.

powermail 3.7 is being used.

TYPO3-Installtool -> TCA-Migration-Check -> Powermail 3.18.2 -> TCA migrations need to be applied

There are plenty of messages regarding powermail in the Typo3 Install Tool TCA Migration (v8.7.1):

The icon path of wizard "RTE" from TCA table "tx_powermail_domain_model_mail['columns']['body']['config']['wizards']['RTE']['icon']"has been migrated to tx_powermail_domain_model_mail['columns']['body']['config']['wizards']['RTE']['icon']" = 'actions-wizard-rte'.

RTE configuration via 'defaultExtras' options are deprecated. String "richtext[]" in TCA tx_powermail_domain_model_mail['types']['1']['columnsOverrides']['body']['defaultExtras'] was changed to options in tx_powermail_domain_model_mail['columns']['body']['config']

The TCA setting 'versioningWS' was set to a boolean value in TCA tx_powermail_domain_model_answer['ctrl']['versioningWS']

The TCA setting 'versioning_followPages' was removed as it is unused in TCA tx_powermail_domain_model_answer['ctrl']['versioning_followPages']

The TCA setting 'versioningWS' was set to a boolean value in TCA tx_powermail_domain_model_field['ctrl']['versioningWS']

Autofill in Google Chrome

In a contact form with just a few fields (name, lastname, mail, message) the autofill function from Google Chrome always puts an e-mail address into the input field. If the form has more fields (zip, city etc.) autofill puts in the "correct" values.
Could that be fixed by renaming labels / input field names?
Thanks for any advice in advance.
Best regards,
Stefanie

TYPO3 7.6.18
powermail 3.18.0
Google Chrome Version 58.0.3029.110 (64-bit)

Marketing informations : Referer and referer domain not set

I enabled the marketing reporting, added the static TS template, my informations are well stored (language, country, mobile...) except the referer.

I did a debug here : https://github.com/einpraegsam/powermail/blob/develop/Classes/Utility/SessionUtility.php#L113

The param $referer is well set, I can see that I come from http://www.facebook.com/
But the next step erase the information, because the array $marketingInfo is already set and does not contain the referer information.

Changing Typo3 backend tool partials

Hey, great extension

I don't know where I can put my question best, hope here is fine.

I want to change the typo3 backend tool layout about the template Resources\Private\Partials\Module\ListOld.html, yes I'm on a typo3 6.2.x version. I want to change that template in a new extension, but it seems that it is not enough to change the partials setup within the typoscript config like this:

plugin.tx_powermail {
    view {
        partialRootPaths.30 = EXT:powermail_bulkorder/Resources/Private/Partials/
    }
}

Powermail: 2.25.2
Typo3: 6.2.19

What did I forget?

Greetings
Tobias Hartmann

Exception while refreshing the submit page

Refreshing the "submit page" generates this error. I am using the latest release of powermail and TYPO3 8.7.1

Exception while property mapping at property path "": It is not allowed to map property "answers". You need to use $propertyMappingConfiguration->allowProperties('answers') to enable mapping of this property.

How to reproduce? Create a simple form with several fields, and make sure you also add a captcha. Activate the confirmation page then proceed to the "submit page". Once the page is loaded and you have all the data displayed, make sure you refresh it. You should now get the error.

precise/generic <error-message> for <length>

the following does not fit everytime :: none or one char within input with length [2, 100]

<trans-unit id="validationerror_validation.9">
	<source>Too many signs given!</source>
	<target state="translated">Zu viele Zeichen!</target>
</trans-unit>

Date fields are not stored

When using date fields, either with our without DatePicker activated, the date is not displayed on the confirmation page and on the submit page, and it is also not available in the finishers.
It is present during the first submit though, so if the validation fails you can still see your old value in the textfield, but it's not passed on to the other pages.

Powermail Marketing Reporting issue

There are no results appearing in Marketing Reporting. In several installations on diferent servers.

  • I have not disabled marketing reporting.
  • And I have added the static template.
  • And Form Reporting statistics are working, for instance.

TYPO3 7.6.15 and PM 3.5.0.
TYPO3 8.5.1 and PM 3.11.2.

  • the cookie fe_typo_user is set (isn't that enough?)
  • typo3conf/ext/powermail/Resources/Public/JavaScripts/Powermail/Marketing.min.js
    is in the footer
  • no JS errors in console

But no marketing data gets written and stored (no cookie and/or session
data, also not in console).

So what do I miss out?

Thanks
Vincent

3.18.0 breaks HTML in OptinMail

Bitte bestätigen Sie mit einem Klick:
https://www.example.de/form.html?tx_powermail_pi1%5Bhash%5D=826d6d4a8e&tx_powermail_pi1%5Bmail%5D=1598&tx_powermail_pi1%5Baction%5D=optinConfirm&tx_powermail_pi1%5Bcontroller%5D=Form&cHash=091c5b3c2f45b3cae7a9a26b3cab7762

Dies sind Ihre Einträge:
<table class="powermail_all"> <tr> <td valign="top"> <b>Name</b> </td> <td valign="top"> Name </td> </tr> <tr> <td valign="top"> <b>Vorname</b> </td> <td valign="top"> Vorname </td> </tr> <tr> <td valign="top"> <b>E-Mail</b> </td> <td valign="top"> [email protected] </td> </tr> <tr> <td valign="top"> <b>PLZ</b> </td> <td valign="top"> 12345 </td> </tr> </table>
sds

No match with Captcha Extension

TYPO3 7.6.15
Powermail 3.18.0
Captcha 2.0.1

Using powermail with the captcha extension by typoscript:
plugin.tx_powermail.settings.setup.captcha.use = captcha

The captcha never matches and gives message:
'Wrong captcha code entered - please try again! '

Error in parsley.min.js

The current used version of parsley.min.js causes an error: "TypeError: t.options.classHandler is not a function". This affects others JS which is used on the page.

Using the latest version (2.7.2) of parsley.js will fix this.

Sorting of export fields get lost after page reload

If you sort, remove or add fields in the extended export settings and reload the backend module (or only change e.g. to reporting view of the same module), all export setting are lost.

At least the possibility (e.g. by tsconfig) to define the initial order of the fields would be fantastic.
A little budget (100 EUR) would be available.

Error when trying to localize a form field

When trying to localize a form field I get en error message:

2: SQL error: 'Incorrect integer value: '' for column 'content_element' at row 1' (tx_powermail_domain_model_field:NEW5916b787d0685799405051)

Powermail: 3.18.0
TYPO3: 7.6.18

powermail-error

error messages in the field partial

Hello

This is not necessarily an issue but more of a question/request.

How would one display the error messages directly in the field's partial? In my custom template each field has 2 columns, the left one holds the label and field(input), while the right one displays the error message/s, if any are present during validation.

I do not want to display them before all the form fields (so have removed the Misc/FormError partial), but to the right side, next to each field.

I can call vh:Validation.ErrorClass to see if an error is present and update the CSS class, but how would I go about showing the actual error message?

I tried calling this in the Partials/Form/Field/Input.html for example, but no error message is displayed:

<f:form.validationResults for="{field.marker}">
	<f:if condition="{validationResults.flattenedErrors}">
		<f:for each="{validationResults.errors}" as="error">
			<p class="error">{error.code}: {error}</p>
		</f:for>
	</f:if>
</f:form.validationResults>

I'm out of ideas so far so any help is more than welcomed.

Thank you

Feature Request: Test Mail to receiver button

The Powermail Plugin offers the possibility to define a custom message sent to both the receiver and the sender of a form. Testing and validating these settings is possible by filling the form in the frontend. As an Integrator i always have to overwrite the customers receiver e-mail address and check if there's also no additional TypoScript that overrules these settings again and revert my changes after successful testing.
A field to enter my e-mail address with a button beneath it to send a test mail with the defined contents would be nice!

Form submit: Scroll down to form anchor

I've got a form on the bottom of a page. When submitting the form, the "is this correct" page is shown - but scrolled to the top. The user has to scroll all the way down to the form again to see this.

Powermail should add an anchor to the form action, so that the browser automatically scrolls down. TYPO3 automatically generates content ID anchors (id="c123") so they could be used.

E-Mails: use TYPO3's defaultMailFromAddress and defaultMailFromName settings

The powermail plugin has settings for "mail to user":

  • "Sender Name (For Confirmation Mail to User)"
  • "Sender Email (For Confirmation Mail to User)"
  • "Subject for Email to Sender (Empty subject disables mail)"

When I do not fill in "Sender Email", the mail does not get sent.

Powermail should fall back to the global TYPO3 mail settings, namely

  • $GLOBALS['TYPO3_CONF_VARS']['MAIL']['defaultMailFromAddress']
  • $GLOBALS['TYPO3_CONF_VARS']['MAIL']['defaultMailFromName']

This way one would not need to fill those fields in the plugins. The subject field would still be responsible to disable mail sending.

Overwrite configuration is not taken into account

Hi,

Just found an issue when sender.name and sender.email are not set (TypoScript or Flexform).
I've got an overwrite configuration (and works fine).

The problems is that replyToName and replyToEmail are empty when creating the senderEmail. Specially in \In2code\Powermail\Domain\Service\SendMailService::prepareAndSend. The call to setReplyTo trigger error as empty strings aren't valid.

Email is not sent at the end!

I don't really know if this is wanted or not?

P.S.: setting sender.name and sender.email with dummy (finally unused) values fix the whole thing.

Kein Caching für "nc_staticfilecache" möglich?

Einen schönen guten Tag,
wir verwenden aktuell ein TYPO3 in der Version 7.16.4 zusammen mit Powermail in der Version 3.6
Nun wollten wir, um das Frontend zu beschleunigen, nc_staticfilecache in der aktuellen Version (3.6) verwenden. Leider sind anscheinend die Seiten, auf denen ein Powermailformular drauf ist, nicht cachebar? Ich glaube mich zu erinnern, das sind in einer älteren Powermailversion (< 3) möglich war? In der Config finde ich auch keine entsprechende Möglichkeit hierzu.

Laut nc_statiffilecache würde das Caching durch Powermail verhindert: "The page has a INTincScript: type: FUNC, userFunc: TYPO3\CMS\Extbase\Core\Bootstrap->run, extensionName: Powermail, pluginName: Pi1"

Field sorting ignored on frontend

I'm working on TYPO3 8.7.1 and Powermail 3.19.0.
I added two fields (City and Province) to an existing form, the backend shows the fields with the correct order
screen_backend
But on frontend they are placed as last inside the page
screen_frontend
Looks like the frontend is ignoring the sorting value.

automatic field repair does not finish

The Powermail backend module offers a possibility to fix localizations of forms, pages and fields.
After udpating Powermail from v2 to v3 i ran the update wizard in the extension manager and clicked all of the "solve problem" buttons, but the last one keeps showing up, even after multiple tries.

bildschirmfoto 2017-05-12 um 13 22 43

If you need a dump of the affected powermail tables you can come over.

Backend record icons missing

In TYPO3 7.6.18, php 7.0.latest, powermail 3.19.0 the icons of all powermail records are missing, resp. displaying the red "broken icon" icon:
grafik

Using the icon registry in ext_localconf.php like this, the icons do display again:

...
$iconRegistry = \TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance(\TYPO3\CMS\Core\Imaging\IconRegistry::class);
$iconRegistry->registerIcon('ext-powermail-field', \TYPO3\CMS\Core\Imaging\IconProvider\BitmapIconProvider::class, ['source' => 'EXT:powermail/Resources/Public/Icons/tx_powermail_domain_model_field.gif']);
...

Then of course also change the icon handling in ctrl part of e.g. EXT:powermail/Configuration/TCA/tx_powermail_domain_model_field.php:

...
// 'iconfile' => ConfigurationUtility::getIconPath(Field::TABLE_NAME . '.gif')
'typeicon_classes' => [
    'default' => 'ext-powermail-field'
],
...

No idea why this seems to be necessary now. Saw it being done like this in EXT:news, where icons worked in the same TYPO3 installation.

Type HTML didn't work since 3.17.0

In my pages i use sometimes fields with type "Show HTML".
Since Powermail 3.17.0 they didn't work anymore, they work only as text.

For example:
I like to have a headline, so i insert
<h4>TEST</h4>
but i didn't get a Headline, i get instead
&lt;h4&gt;TEST&lt;/h4&gt;

I use Typo3 7.6.16 or 7.6.18
I test Powermail in Version

  • 3.17.0
  • 3.18.0
  • 3.18.1
  • 3.18.2

live example: http://www-test.bib.uni-mannheim.de/anschaffungsvorschlag/

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.