Nahuai Badiola

Good to know, but after almost 4 months with no news I stopped using it.

I’m glad you fixed it but I doubt I’ll ever use it again, too risky.

Cheers.

Cool!

Glad to help.
Looking forward to try the new update, I hope it solves the problem ??

Cheers.

Hi,

thanks for the prompt answer.

I didn’t provided the when and why info, because nothing special happened to explain the error.
So right know I don’t know how to replicate the error (other than create a page with your blocks). If I do I’ll let you know.

In the other hand, yes, I did captured the console info.
This is one example:

Block validation: Block validation failed for atomic-blocks/ab-testimonial (
Object

attributes: {testimonialName: {type: “array”, selector: “.ab-testimonial-name”, source: “children”}, testimonialTitle: {type: “array”, selector: “.ab-testimonial-title”, source: “children”}, testimonialContent: {type: “array”, selector: “.ab-testimonial-text”, source: “children”}, testimonialAlignment: {type: “string”}, testimonialImgURL: Object, …}

category: “atomic-blocks”

description: “Add a user testimonial with a name and title.”

edit: function()

icon: {src: “format-quote”}

keywords: [“testimonial”, “quote”, “atomic”] (3)

name: “atomic-blocks/ab-testimonial”

save: function(props)

title: “AB Testimonial”

Prototipo de Object
).

Expected:

<div style=”background-color:#f2f2f2;color:#32373c” class=”wp-block-atomic-blocks-ab-testimonial right-aligned ab-font-size-16 ab-block-testimonial”><div class=”ab-testimonial-text”><p>Vicky supo adaptarse a nuestras peticiones y fue un trato muy agradable. Se hace muy cercana y amena, por lo que todo es mucho más sencillo.</p></div><div class=”ab-testimonial-info”><h2 class=”ab-testimonial-name” style=”color:#32373c”>Beatriz F.</h2><small class=”ab-testimonial-title” style=”color:#32373c”>Getxo</small></div></div>

Actual:

<div style=”background-color:#f2f2f2;color:#32373c” class=”wp-block-atomic-blocks-ab-testimonial right-aligned ab-font-size-16 ab-block-testimonial”><div class=”ab-testimonial-text”><p>Vicky supo adaptarse a nuestras peticiones y fue un trato muy agradable. Se hace muy cercana y amena, por lo que todo es mucho más sencillo.</p></div><div class=”ab-testimonial-info”><h2 class=”ab-testimonial-name” style=”color:#32373c”>Beatriz F.</h2><small class=”ab-testimonial-title” style=”color:#32373c”>Getxo</small></div></div>

I hope this info helps you to understand the problem.
If you need any more details just let me know.

Thanks!

Looks like it was a problem with another website on the same server…

Thanks to the info from the hosting guy and the email support seems that the error is gone for good.

In case someone runs into the same error here is the support reply that may help you:

In essence, the configuration path isn’t correct. Try modifying your open_basedir setting to match the working directory of the site, which should solve this issue. Take a look at: https://stackoverflow.com/a/7494262 ??

Thanks for the email support, specially Jack ??

I’ll mark it as solved and I hope I don’t have to reopen it.

Hi,

The error is back.
I wrote you an email with more info I hope it helps to solve the problem.

Thanks.

Hi again,

No, the weird thing is that none of those errors were triggered by any change on plugins or WordPress.

The 3.7.5 update didn’t solve the error at the moment (it was still displayed on the dashboard), but after few hours it was gone and it didn’t reappear since then. So, almost one week without problems, j.

I’m keeping my fingers crossed but I’m a bit afraid to do the update to 3.7.6…

I know nothing of this makes sense but with the new info ?can you think on any reason that explains this behavior?

Thanks, I’ll keep you posted.

The error is back, is intermittent, one day no error, next day error ??

I’m doing test with the hosting guy but still not luck.

The hosting is running php 5.6.33 (I told him to update it, but he can’t yet)
Can it be the problem?
In some places I red that Swiftmailer requires php 7 or higher but Mailpoet 3 only requires 5.3…

I don’t know, just trying to figure it out.

Hi again,

the error is gone. I don’t know how but it looks like it was something related with the server. Even if the hosting guy said there was no significant change.

In any case, thanks a lot for the help in the support chat. Even if we didn’t crack it, Kim was really helpful with the troubleshooting.

Cheers.

@koyi I see that you had a similar problem
Did you find the solution?

Thanks!

Sorry for the delay.
After the last updates it seems to work fine.

Thanks for the help!

That’s great!
Looking forward to have the new version.

Thanks @ehsantikweb, great job.

Hi,

I also think it would awesome to have more fields to map (beyond name/surname and email). Specially now that the GDPR is going to be mandatory it will be very useful to map the user consent to the terms and conditions of your web.

?Do you have any plan to release this feature in the near future?

Thanks!

Hi Jack,
I guess you are referring to the system info, right?
Here it goes:

name: xxx
email: la.com
PHP version: 7.0.28
MailPoet Free version: 3.5.0
MailPoet Premium version: N/A
MailPoet Premium/MSS key: 
WordPress version: 4.9.4
Database version: 5.6.39-cll-lve
Web server: Apache
Server OS: Linux cp338.webempresa.eu 2.6.32-673.26.1.lve1.4.18.el6.x86_64 #1 SMP Fri Oct 21 11:58:14 EDT 2016 x86_64
WP_MEMORY_LIMIT: 40M
WP_MAX_MEMORY_LIMIT: 512M
WP_DEBUG: false
PHP max_execution_time: 300
PHP memory_limit: 512M
PHP upload_max_filesize: 55M
PHP post_max_size: 55M
WordPress language: es_ES
Multisite environment?: No
Current Theme: Imagely Ansel (version 1.0.6)
Active Plugin names: gravityforms/gravityforms.php, akismet/akismet.php, bloom/bloom.php, cookie-notice/cookie-notice.php, divi-builder/divi-builder.php, genesis-404-page/plugin.php, genesis-translations/genesis-translations.php, google-analytics-dashboard-for-wp/gadwp.php, google-analytics-for-wordpress/googleanalytics.php, mailpoet/mailpoet.php, meow-gallery-pro/meow-gallery-pro.php, monarch/monarch.php, smart-recent-posts-widget/srpw.php, so-css/so-css.php, subscribe-to-comments-reloaded/subscribe-to-comments-reloaded.php, table-of-contents-plus/toc.php, updraftplus/updraftplus.php, we-cachepress/we-cachepress.php, weimgoptimizer/weimgoptimizer.php, wordpress-seo/wp-seo.php, wp-external-links/wp-external-links.php, wp-featherlight/wp-featherlight.php, wplr-sync/wplr-sync.php
Sending Method: PHPMail
Sending Frequency: 50 emails every 15 minutes
Task Scheduler method: WordPress
Cron ping URL: https://www.xxxxx.com?mailpoet_router&endpoint=cron_daemon&action=ping
Default FROM address: xxxx.com
Default Reply-To address: xxxx.com
Bounce Email Address: xxxx.com
Total number of subscribers: x3

I hope it helps to debug it.

Cheers,
Nahuai

• This reply was modified 7 years ago by Nahuai Badiola.
• This reply was modified 7 years ago by Jan Dembowski. Reason: Fixed formatting

Hi @wysija!

Yes I do.
Indeed I did several test using different lists, but none of them got the new suscribers.

Is like the info of the comment box is arriving (sent) to Mailpoet.

Do you know why could it be?

Thanks!

• This reply was modified 7 years, 3 months ago by Nahuai Badiola.

I’m glad to hear that.

I guess it will be mentioned on the changelog when is ready, right?

Thanks!