Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Apr 16 22:38

    PowerKiKi on master

    Deprecate the entire project (compare)

  • Mar 29 10:23

    fabarea on travis_debug

    (compare)

  • Mar 29 09:45

    fabarea on develop

    Update composer.json (compare)

  • Mar 29 09:41

    fabarea on develop

    Update composer.json (compare)

  • Mar 29 09:40

    fabarea on develop

    Update ext_emconf.php (compare)

  • Mar 29 09:39

    fabarea on develop

    (compare)

  • Feb 14 07:13

    PowerKiKi on 4.0.0

    (compare)

  • Feb 14 07:13

    PowerKiKi on master

    4.0.0 This release is mostly b… (compare)

  • Feb 14 03:06

    PowerKiKi on master

    Don't advertise non-supported T… (compare)

  • Jan 30 05:03
    PowerKiKi milestoned #169
  • Jan 30 05:03
    PowerKiKi labeled #166
  • Jan 30 05:03
    PowerKiKi labeled #169
  • Jan 30 05:03
    PowerKiKi commented #169
  • Jan 29 11:39
    wakoch opened #169
  • Jan 29 10:57
  • Jan 29 10:57
    wakoch starred Ecodev/newsletter
  • Jan 24 08:34
    MoppieMop commented #63
  • Dec 04 2018 22:41

    PowerKiKi on develop

    Remove deprecated sudo from Tra… (compare)

  • Oct 15 2018 00:58
    PowerKiKi synchronize #167
  • Oct 14 2018 13:01
    matthiaswe synchronize #167
chris
@cdaecke
is it somehow possible to deactivate injectLinksSpy() completely?
or is it only possible to deactivate link tracking by using the $notrackMarker?
chris
@cdaecke
I have temporary removed the foreach loop in injectLinksSpy(). This will speed up the process very much, but still needs a little more than one minute for sending 25 emails. When calling the scheduled task from the TYPO3 backend it is much faster (about 5-10 seconds).
so i guess this is realy related to the server and not your extension?!
Batman777
@Batman777

I have installed the Newsletter ext. Everything works fine.:-) Newsletters are being send, tt-address submissions are beeing recognized etc.

The "only" problem I have is that it looks like the newsletter template can't be found and therefore my newsletters are empty!

Typo 6.2.31

And "Hello" of course ... :-)
My Ts Setup for newsletter template in sysfolder
Adrien Crivelli
@PowerKiKi
@cdaecke the difference you get from Backend and CLI is really suspicious. I can't think of anything that could explain that difference from the top of my head. But maybe something differs in your environnement that trigger an unexpected behavior in Newsletter or more generally TYPO3. You could try do dump versions of PHP, its extensions, $_ENV and so on... and compare Backedn vs CLI
@Batman777 what does "newsletter template can't be found" means ?
Batman777
@Batman777
Hi Adrian .. well .. I don't get any error .. instead it says "Newsletter was sent" .. Also i get the testnewsletter .. But Subject and content are empty
That#s why I assume that the template could not be found
Adrien Crivelli
@PowerKiKi
I am not familiar with TS and Newsletter works without any custom TS at all. So I am not sure what you are trying to do with that, but I suppose there may be a misunderstanding on how Newsletter works
Did you try a simple test without any TS at all ?
Batman777
@Batman777
Nope ... was just thinking about it ... :-)
one second
Adrien Crivelli
@PowerKiKi
Also did you try the preview feature before sending anything ?
Batman777
@Batman777
Where is the preview function? Have not seen it
Adrien Crivelli
@PowerKiKi
And finally did you double-check the messages on the status page https://raw.githubusercontent.com/Ecodev/newsletter/master/Documentation/Images/Newsletter_-_Status.png ?
Batman777
@Batman777
preview says "The newsletter HTML content does not validate. The sending is aborted. See errors: a:1:{i:0;s:82:"Sie verwenden Bildern im CSS. Die meisten E-Mail Clients unterstützen dies nicht!";}"
even though I only have one text content
Screenshot_1.jpg
Adrien Crivelli
@PowerKiKi
then you'll have to fix that first, remove all CSS that contains references to images
Batman777
@Batman777
remarked all TS Settings .. unfortunately still does not work
Adrien Crivelli
@PowerKiKi
I really can't help you about TS
but you should be able to debug easily, because Newsletter give you the exact URL it is using to retrieve the content.
In your case it's /index.php?id=735
debug that page, independently of Newsletter, to remove all CSS that refers to images, and do whatever you want with TS. Only then you can start to use Newsletter
Batman777
@Batman777
When I look at the page 735 - after I remarked all TS -I see my maintemplate with the text content I entered. That is probably the reason why I get the error with images. Therefore I wonder how to embed my own template?
777.png
Does not seem to work
Batman777
@Batman777
Well .. I now changed the TS to the following:

page = PAGE
page.typeNum = 0
page.100 = FLUIDTEMPLATE
page.100 {
format = html
file = fileadmin/templates/XXX/tmpl_newsletter.html

variables {
content < styles.content.get
content.select.where = colPos = 0
}
}

Screenshot_1.jpg
Now there is a 500 Server Error :-(
Adrien Crivelli
@PowerKiKi
All of this is unrelated to the Newsletter extension, open the page in your browser, and debug with your standard workflow
(because under the hood Newsletter use cURL to get the content, so it really is juste like any other external visitor browsing your page)
Batman777
@Batman777
That's the error I get.
Screenshot_1.jpg
No idea where Newsletter.html / newsletter.html - Layouts/newsletter come from ...
Adrien Crivelli
@PowerKiKi
@Batman777 I am pretty sure this has nothing to do with Newsletter itself and if you disable and delete the Newsletter extension it will still throw the same error. And thus I can't help you, because it is specific to your TYPO3 install
Magic Labs
@MagicLabs1_twitter
Hello
How can i display newsletter form on front end of my website?
by using EcoDev Newsletter extension>
Adrien Crivelli
@PowerKiKi
there is no form in Newsletter
you have to build it, with the tools that best fit your use-case
d3rt
@d3rt
does anybody have a idea for following problem: If I start the task in the sheduler manually the newsletter will be sent correctly, but if the cronjob activates the task in the sheduler the mail is empty. The test mail script in sheduler from TYPO3 send mails correctly
Adrien Crivelli
@PowerKiKi
@d3rt, did you try what I suggested by email ?
d3rt
@d3rt
@PowerKiKi yes, but this dosen`t work. I can see in the Debug that the content & subject in the Newsletter Class is empty and the mail would be sent. After the email is sent, the Newsletter Class is correct. But for the next Mail the problem is the same...I thought is something with server cache...