Forum Activity for @ken-rich

Ken Rich
@ken-rich
08/07/23 11:45:06AM
926 posts

Email Notifications Plain Text Only?


Using Jamroom

I am not sure if this is related to the recent CORE change but I have noticed on both my networks that email notifications are no longer using HTML even though that option is checked.

It is easily reproducible by sending test emails. What could be causing this?
updated by @ken-rich: 11/07/23 12:08:58AM
Ken Rich
@ken-rich
08/06/23 04:22:08PM
926 posts

Signup Error


Using Jamroom

I'll get my server guy to check that other stuff - thanks.
Ken Rich
@ken-rich
08/06/23 04:20:57PM
926 posts

Signup Error


Using Jamroom

After I got my updates done I reenabled the Geo module but signups failed again, so I had to disable it again. I then confirmed signups work again when it's disabled - so there is definitely a problem there.
Ken Rich
@ken-rich
08/06/23 04:09:39PM
926 posts

Signup Error


Using Jamroom

Scratch that - I just tried another integrity test and after that, my updates finally went in. So this network is good now with no Geo.

However, on my main network, the integrity check fails if I check "Repair Modules".

I used the new functionality to check individual modules and I can get them to pass if I don't try too many at once. All but the "Subscriptions" module - that one won't pass even if tried by itself.

The Reset Caches function also fails if "All template files" is checked.

Any ideas on those issues?
Ken Rich
@ken-rich
08/06/23 03:47:29PM
926 posts

Signup Error


Using Jamroom

However, the good news is that signups are working again with the Geo module disabled.
I just don't know why I am still having trouble with updates.
Ken Rich
@ken-rich
08/06/23 03:40:49PM
926 posts

Signup Error


Using Jamroom

I disabled the Geo module but still can't get the updates to work.
It spins and spins, hanging on the line...
"validating filesystem is prepared for updates"
Ken Rich
@ken-rich
08/06/23 03:26:27PM
926 posts

Signup Error


Using Jamroom

The screenshot shows my error log in the admin panel is empty.

On the server, I have a data/logs/debug_log but no data/logs/error_log

The data/logs/debug_log has entries but the latest is last month and unrelated. The permissions are rw-r-r

On the server I also see an access log and an error log (under logs - not data/logs). The error log has something signup related at the end

module.php(314): view_jrUser_signup_save()
#3 /usr/share/nginx/pinkbunnies.club/public_html/modules/jrCore-release-7.0.0/router.php(119): jrCore_run_module_view_function()
#4 {main}
  thrown in /usr/share/nginx/pinkbunnies.club/public_html/modules/jrGeo-release-2.3.0/include.php on line 392" while reading response header from upstream, client: 174.113.80.37, server: pinkbunnies.club, request: "POST /user/signup_save HTTP/2.0", upstream: "fastcgi://unix:/run/php-fpm/jamroom.sock:", host: "pinkbunnies.club", referrer
I thought the issue might be related to the new CORE because I can't install 3 of my updates (users, profiles, search). However, I rolled back the core update and the signup issue persisted so I updated the core again.
Screenshot 2023-08-06 at 19-43-07 Error Log.png Screenshot 2023-08-06 at 19-43-07 Error Log.png - 12KB

updated by @ken-rich: 08/06/23 03:34:19PM
Ken Rich
@ken-rich
08/06/23 02:38:39PM
926 posts

Signup Error


Using Jamroom

I am not seeing anything in the error log,
It just says "No PHP Errors at this time"
Ken Rich
@ken-rich
08/06/23 02:22:26PM
926 posts

Signup Error


Using Jamroom

I am getting this error (see screenshot) when a new member tries to signup and hits save.
Any idea what is causing this? /user/signup_save
signup.JPG signup.JPG - 57KB

updated by @ken-rich: 11/05/23 02:51:27PM
Ken Rich
@ken-rich
06/03/23 09:52:33AM
926 posts

Foxycart no longer working


Installation and Configuration

Foxycart gave me a code to hide the shipping charge since it is already in the subtotal.

I did two more tests for the shipping charge adding to the Profile Payout. Both were successful, I don't know why it failed before.

So I think the issues are fixed at this point - thanks for your help.
  2