jamroller

Understood and done. Thanks.

Thanks for the feedback. I have tried what you suggested, but rechecks don’t seem to resolve the issue.

Sorry…I never saw the initial reply. Here is the link to the screenshot:

https://destination-bbq.com/wp-content/uploads/2023/01/Screenshot-2023-01-08-at-8.10.55-PM.png

I currently have 41 new broken links. As before, one is an Amazon short link while the rest are Yelp links. Here are a few that are currently listed as 503s:

https://amzn.to/34BRQcm

https://www.yelp.com/biz/the-spotted-pig-bbq-fair-play?sort_by=rating_desc

https://www.yelp.com/biz/521-bbq-and-grill-fort-mill?sort_by=rating_deschttps://www.yelp.com/biz/521-bbq-and-grill-fort-mill?sort_by=rating_desc

https://www.yelp.com/biz/521-bbq-and-grill-tega-cay-2?sort_by=rating_desc

https://www.yelp.com/biz/bellys-southern-pride-bbq-and-catering-lexington?sort_by=rating_desc

hi,

I just tested…the problem remains. I am fully up-to-date on all plugins.

That worked. Thanks so much for the amazingly prompt replies.

I am pretty sure I would have deleted it like one does with most plugins…Deactivate….Delete.

Will do so.

Thanks @wfgerald, but I don’t have WF installed at all. I deleted it a month or so ago.

Interesting side note: I happened to be doing some database work and ended up needing to restore a backup because I screwed something up. As part of that process, I had to delete all the existing tables so the backup would import. Funny thing is that after deleting the existing tables, suddenly there showed up a new table called wp_sm_sessions! (See here: https://destination-bbq.com/wp-content/uploads/2019/03/Screen-Shot-2019-03-03-at-6.54.07-PM.png)

Now, the table was deleted for the import, but it is strange that it auto-generated after the other tables were deleted and has not respawned after import, isn’t it? Is there a possible conflict among the existing tables? Is that a thing?

I will continue to investigate for the near future. If I figure it out, I will share with you here. Otherwise, I feel like I will have no choice but to find another plugin to take Stripe Payments. Thanks again.

More info: occasionally, the error log reads this line:

WordPress database error Table ‘yearbop3_wp328.wp_sm_sessions’ doesn’t exist for query SHOW FULL COLUMNS FROM wp_sm_sessions made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘plugins_loaded’), WP_Hook->do_action, WP_Hook->apply_filters, wp_session_start, WP_Session::get_instance, WP_Session->__construct, WP_Session_Utils::update_session

@pderksen thanks for your feedback. Unfortunately, the suggestions do not solve my problem.

As you can see here: https://youtu.be/Cilad-huoNM

I have tried your suggestions to no avail. As for the plugin, I do not have that, nor do I believe I have anything like it

As you can also see in the video, the only thing that stops the errors is to deactivate WPSP.

Update on what I’ve tried in the interim:

Found another similar thread and tried both suggestions: https://www.ads-software.com/support/topic/session-error-with-2-0-7-version/

Did not find to delete the sm_session_db_version in the wp_options table so not an option
Deactivated and reactivated the plugin — no change
Deleted and reinstalled the plugin — no change

Set the SIMPLE_PAY_USE_PHP_SESSIONS constant to true in your wp-config.php — no change.

Error logs still blowing up with the same error every few seconds.

Note: when I deactivate the plugin, the error messages stop. I can deactivate the plugin, delete the error logs. Go about my business for a while. Check on the logs later and no new error log is even generated in the root or in wp-admin dir.

Note Also: when I finally discovered the problem, my two error logs were huge, with one a few MB from 1 GB!

Other notes: I have also repaired and optimized all databases using phpMyAdmin.

Thoughts?

• This reply was modified 5 years, 9 months ago by jamroller.
• This reply was modified 5 years, 9 months ago by jamroller.
• This reply was modified 5 years, 9 months ago by jamroller.

Thanks for the feedback. I have always wondered about SLPlus. Interestingly, the developer of SLPlus and I live in the same place — Charleston, SC. So, for reasons of commonality, I was immediately drawn to that option. Thanks again.

Do you mind if I ask why you switched over? I really looked hard at SLPlus when building the map on my site, but, frankly, went with the less expensive (free) option. I really like WPSL. I think Tijmen is great and has a winner on his hands, but because of his freelance work, the wait for the official 2.0 (and later the premium option) have been VERY long. I look forward to being able to pay him for his efforts when premium comes out.

Thank you for the feedback.

While I believe #1 is important, I would argue #2 is critical.

I personally was trying to find a restaurant to try during our recent trip. I was VERY frustrated by the inability to find my current location because of #1 above. I even went into the iPhone’s settings and cleared the history and website data, but nothing I did solved the problem of #1.

I found later that it would not have made any difference because of the issue outlined in #2. I’ll say again that #2 is a big deal to the end user.

I love your plugin and have said many times I am eager to pay you for the premium version, but if #2 remains a problem, I will have to consider looking around for other options because I think it is imperative that the directions provided be as location specific as possible. Anything less is pointless.

In the heat of the moment, especially when driving through unfamiliar areas, the current information provided to drivers is inadequate…not to mention extremely frustrating.

As for #3, I would tell you that I thought it worked as one would expect, but the screenshot you see was basically the same result I got on the iPhone on the cellular network. So both the laptop and the phone — on two different networks — yielded the same result. Note: I was using Safari in both cases, however. I did not try a different browser on either.

Again, I thank you for a great plugin and your very responsive support. I am really looking forward to the public version of 2.0 and, beyond that, the premium version, but I do sincerely hope these issues can and will be addressed as soon as possible.

Thanks again.