sootsnoot

With Force Login deactivated, it seems that the Find Events button works properly, and having found an event, clicking the List, Month, or Day buttons also work, with output limited to just the found event. The cases where it appeared not to work may have been because I was trying it on my phone, where the responsive layout can make things confusing. On my desktop PC, it all looks good.

So the only real problem is the 503 error on clicking any of those buttons when Force Login is activated. Please let me know how I can send login credentials to you privately so that I can reactivate that plugin and you can investigate the 503’s when logged-in.

Thanks,

Okay, I’ve deactivated Force Login. The buttons for List, Month, and Day now seem to work. Find Events sometimes does work, but sometimes does not find listed events.

Let me know when and how to send you login credentials, so I can reactivate Force Login, so you can investigate the 403 error thrown by all of those buttons, since that is more of a problem for our members. ??

As I explained, the problem occurs only with the “/events” slug which is predefined by this plugin. It does not affect the shortcode since the shortcode does not display any of the four broken buttons (Find Events, List, Month, Day).

Regarding the Force Login plugin, that’s a pretty simply plugin that checks is_user_logged_in(), and if so does nothing, but if not (and the request is not for the login page), then returns a 403 (forbidden) status and displays the login page. You can see in the devtools console output I provided that clicking any of those 4 buttons results in a 403 error. And as I also said before, that would be expected if the The Events Calendar did not take care to provide the logged-in cookies in the XHR request.

I already provided the exact url showing the problem in my first post – but of course that will take you to the login page, since you’re not logged in and the Force Login plugin is activated. I could temporarily deactivate Force Login so you can investigate why Find Events always returns Not Found. Or I could send you login credentials so you could login and investigate why clicking any of the 4 buttons has no visible effect unless using devtools where it shows the 403 error.

Please let me know how to proceed, thanks!

Well, I tried editing file the-events-calendar\src\resources\js\custom-tables-v1\ct1-upgrade.js and just before the request.send() at line 105, I added request.withCredentials = true; and then I minified it, replacing the-events-calendar\src\resources\js\custom-tables-v1\ct1-upgrade.min.js. But unfortunately, that didn’t help, I’m still seeing the same error in the devtools console, and I don’t know why. Can you fix it correctly? I certainly don’t want to leave Force Login deactivated. And then when you eliminate the error, take a look at why the Find Event button doesn’t find strings that appear in the event title or text?

I am happy to do that. Not my intent to rake you over the coals. As I’ve said, I think you do a fabulous job supporting this plug-in, and I am grateful for it!

Well, Javier, I updated this plugin to the new 1.27.8 and tried again with the corrected csv file and the updated Melapress Login Security 2.0.0 activated. Unfortunately the problem persists. Here is the email:

<pre>
WordPress version 6.6.2
Active theme: Divi (version 4.27.2)
Current plugin: Import and export users and customers (version 1.27.8)
PHP version 8.0.30.2



Error Details
=============
An error of type E_ERROR was caused in line 33 of the file /var/www/wp-content/plugins/import-users-from-csv-with-meta/addons/melapress-login-security.php. Error message: Uncaught Error: Class "PPMWP\PPM_WP_History" not found in /var/www/wp-content/plugins/import-users-from-csv-with-meta/addons/melapress-login-security.php:33
Stack trace:
#0 /var/www/wp-includes/class-wp-hook.php(324): ACUI_MelapressLoginSecurity->import(Array, Array, 41, Array, Array, Array, false, false, true, true)
#1 /var/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
#2 /var/www/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#3 /var/www/wp-content/plugins/import-users-from-csv-with-meta/classes/import.php(632): do_action('post_acui_impor...', Array, Array, 41, Array, Array, Array, false, false, true, true)
#4 /var/www/wp-content/plugins/import-users-from-csv-with-meta/classes/import.php(815): ACUI_Import->import_user(2, 15, Array, Array, Array, Array, Array)
#5 /var/www/wp-content/plugins/import-users-from-csv-with-meta/classes/import.php(244): ACUI_Import->import_users('/tmp/phpblFdjA', Array, false, false)
#6 /var/www/wp-content/plugins/import-users-from-csv-with-meta/classes/import.php(25): ACUI_Import->fileupload_process(Array, false)
#7 /var/www/wp-includes/class-wp-hook.php(324): ACUI_Import->show('')
#8 /var/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters('', Array)
#9 /var/www/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#10 /var/www/wp-admin/admin.php(259): do_action('tools_page_acui')
#11 /var/www/wp-admin/tools.php(40): require_once('/var/www/wp-adm...')
#12 {main}
  thrown
</pre>

And as before, deactivating Melapress Login Security resolves the problem.

I agree with you – I don’t even know how that line got there, so it’s hard to imagine anyone else doing something like that. The documentation clearly specify the field names to use, and that isn’t one of them.

Melapress Login Security just released an update, to version 2.0.0. So I updated and reactivated it. I still get the “Error: Class “PPMWP\PPM_WP_History” not found”, with an emailed traceback that looks similar but with different line numbers. Deactivating Melapress Login Security before import still fixes the problem. Guess I just need to wait for your next update to see if I still get it with version 2.0.0 of Melapress activated.

Oh my, very embarrassing! I don’t know how that got there. I thought maybe the export did it, but apparently not. Anyway, it got there very early on in my testing, and I didn’t think anything of it, and just tweaked the values starting at the 3rd row, like the email address, which did wind up getting imported.

Sorry for being such a dope.

OTOH, it would be nicer if the import tool would report an error for any csv file containing a first row that did not begin with “user_login”. I know you’re very busy making this free plugin even better, but detecting that error should be “really easy” :-)…

Yes, I’m using Libre Office Calc. I open the csv file with Calc, which does not complain about its validity, edit a character or two, and then save it back to the same csv file. Here is the exact csv file I’m using. This produces the error Invalid email “user_email” on the Import page. I then go to Users on the admin panel, and see user TEST created with Username, First name, nickname, and display name all set to TEST. And the email delivered to [email protected] contains:

<pre>
URL to login = https://wp.freestylefarm.org/wp-login.php

Username   = TEST

Password   = NGm6qs3A4MwJ
</pre>

So the names and password specified in the csv file were all ignored.

Other emails, like the one to admin saying a new user was added, or a password was changed, do arrive in a reasonable timeframe, so it’s not a configuration issue. As far as I can tell, emails don’t arrive when one of two problems I reported happen:

1. the email address has a gmail-style “+” in it, causing an error to be reported on the Import page (https://www.ads-software.com/support/topic/cannot-import-email-with-gmail-syntax-and-poor-error-message/)
2. the Melapress Login Security plugin is activated, causing a critical error to be reported on the Import page, and an email to be sent containing a traceback (https://www.ads-software.com/support/topic/uncaught-error-class-ppm_wp_history-not-found/)

You’ve said the second problem is resolved in the next update, which I haven’t yet seen. I think the first problem still occurs, but I want to wait until I install the update to see if it still happens. That one seemed to be a little flakey, where sometimes I could reproduce it and sometimes I couldn’t.

BTW, I absolutely understand and appreciate the effort you put into the fabulous support you provide for this valuable free plugin!

And it appeared to give all of the name fields, like Name, display_name, nickname, user_nicename, the value TEST, the user_login.

Well, actually, I’m seeing the problem again now. Guess I didn’t have other emails like that: https://drive.google.com/file/d/1DrMihKrr8SipzLmapF8oYs1JE02MdAH9/view?usp=sharing

This import basically worked, in that the user got created as a subscribner with the specified email address. However, they were not given the specified password of Please-Change, but rather a random password:

<pre>
Your data to login to this site is:

URL to login = https://wp.freestylefarm.org/wp-login.php

Username   = TEST

Password   = iTAE*h2@Dj^^
</pre>

• This reply was modified 4 months, 2 weeks ago by sootsnoot. Reason: Show the email with login credentials

I’m still getting this error, but I have found that deactivating Melapress Login Security 1.3.1 makes it go away…

So sorry, I’m embarrassed that I didn’t see that tab! It couldn’t be more clear, and right near the top, too!