marvel32

I had the same configuration (sender address not the same as smtp-address) and that worked for years up to version 2.2.0. After updating to 2.3.0 this suddenly stopped working. Is this a ‘feature’ of the new version?

Sorry, I found out the problem: it was LastPass that filled that field. Please remove this item.

In 3.6.10 the problem still exists. What is the planning for fixing this?

Thank you for your quick answer! I never expected the theme to include coding for WP-Members, but appearently it does. Changed wpmem_block into wpmem_is_blocked and everything works again. Thanks again!

Hello Chad,

Unfortunately, the new WP-Members breaks my site when I am NOT logged in.

Fatal error: Call to undefined function wpmem_block() in /home/verenigingvoorst/public_html/wp-content/themes/rttheme18/rt-framework/functions/theme_functions.php on line 601

When I deactivate WP Members site works again. Any clue?

Site is https://www.verenigingvoorstoelmasseurs.nl/

On https://www.verenigingvoorstoelmasseurs.nl/contact/ the error message is visible.

The error is on the homepage and a few other pages. Page https://www.verenigingvoorstoelmasseurs.nl/lid-worden/ works normally. Odd.

• This reply was modified 6 years, 8 months ago by marvel32. Reason: Added links
• This reply was modified 6 years, 8 months ago by marvel32. Reason: More information

Thank you for your answer!

I think WP Members does use the standard WordPress user profile to store data, so that opens possibilities.

I added a field dbem_contact and gave that a value for my own account. I then did a booking, but the (contents of that) field did not appear in the booking table.

I am doing something wrong, I guess.

Should I somewhere write #_CONTACTMETA{dbem_contact} in the settings? And could I also use, for example, #_CONTACTMETA{mobiel_telefoonnummer} ?

We use the WP Members-plugin, with several fields in the user records. Relevant Meta Keys are phone1 and mobiel_telefoonnummer.

It would be really great if I could somehow tell Event Manager to copy the content of both these fields (or even more fields) to the reservation.

Can this be done with the Pro version of your plugin?

• This reply was modified 7 years, 9 months ago by marvel32.

Maybe I did not explain clearly what the problem is.

For a guest user to make a reservation he has to fill in his name, e-mailaddress and phone number. Excellent, no problem.

When a member is logged in, he only clicks a button and does not have to fill in anything. So far so good.

Then, from the backend, when I look at the bookings, for member-tickets only name and e-mailaddress is listed. The field phone number is still empty. And that is my problem: how to get the members phone number in the booking?

Yes.

I noticed that sites hosted by provider #1 are all right, and sites hosted by provider #2 are affected. Moving a site from #1 to #2 gives the errors. It is not the moving itself: sites that have always been hosted by #2 also give the problems. This I why I thought it may have something to do with levels or configuration of PHP or other software (MySQL).

Something else weird comes up: on a site with erroneous dates: if I sort the list by date (from within the plugin) the sort is not correct! If I sort within phpMyadmin the sort is correct. Isn’t that bizar?

Pleasy let me know if there is anything I can do to provide you with extra information. Maybe it is already helpful that you experience the problem yourself too.

Site 2 may be especially interesting. In the database export timestamps were correct. After moving to another provider they were corrupted.

As explained earlyer I deleted the erroneous records and reloaded from the export. Then everything was ok.

But now: some records are corrupt again! You would expect mail_id in the same order as the timestamps but they are not: there are a few non-consecutive records with the timestamp 2017-04-17 23:40:51. These mails have the IP-adress of the current host.

Can it have something to do with PHP levels?

By the way: on site #4 column host is empty. On site #1 it is empty until 2016-11-05.

Thank you for your quick response! I checked the way you pointed out, with following results:

Site 1 (everything ok): on update CURRENT_TIMESTAMP
Site 2 (problems): on update CURRENT_TIMESTAMP
Site 3 (problems): on update CURRENT_TIMESTAMP
Site 4 (problems): on update CURRENT_TIMESTAMP

On a newer website, only a couple of months old, I also found the attribute “on update CURRENT_TIMESTAMP” set.

I manage several websites using this plugin, and found some interesting results.

For example: on site 1 the plugin holds 346 mails, all with correct dates, the oldest from 2014-08-31. The plugin is updated regularly.

On site 2, there are 330 mails, almost all of them have the date 2017-04-17. From the content I can see the oldest mail must be before 2014-08-26. I recently moved this site to a different provider and I still had the export of the database at hand. In the WPML-records the dates were correct. So maybe the move corrupted it? I deleted the records from the database and imported the ones from the backup and this went ok, so this was not the problem.

On site # 3, there were 1.106 mails, records 1 to 105 had the date 2017-04-19 (which is wrong), record 106 had the correct date: 2015-07-03.

Finally, site # 4. The database shows 222 wpml_mails-records. Mail_ids 1 to 17 dated 2017-04-28, nr 18 is correct (2015-09-15), nrs 19 to 24 wrong, nr 25 correct, nrs 26 to 29 wrong, nr 30 correct, etc. I can leave this table as it is, because this site is not so important. Maybe it is helpful in analyzing this problem.

I did not quite understand your question regarding the timestamp field in the wpml_mails table. On all sites it holds dates in the format as shown above. Is this the answer you need?

Please let me know if there is any information I can give you to help understand what is going wrong.

I encounter the same problem. Also it took quite a while for the message to be send to the administrator, although I can live with that.

Any news on progress on this item?

Great! Works like a dream! Thank you so much!