Losing Meetings Page Link Each Night #1130
-
|
Each night the link to our Meetings page is lost. This started with the latest update to the 12-step-meeting-list. Deactivating and reactivating the plugin seems to work, Resaving our permalinks also works. However this has had to be done each day since the latest update. I have attempted to deactivate other plugins I thought might be conflicting to no avail. We are on the latest version of WordPress and have all plugins up-to-date. |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 4 replies
-
|
hm, sorry about that! we're investigating the possibility that there's an incompatibility with certain plugins. is the page in question https://akronaa.org/meetings/? |
Beta Was this translation helpful? Give feedback.
-
|
Yes. I happened to be working late tonight and had the page up about 10 pm.
I noticed it lost the link around 10:20. I had wondered when it was
happening so I will take a look tomorrow to see if one of our backups is
running around that time. I tried turning off YostSEO yesterday but that
didn't work.
…On Mon, May 15, 2023 at 10:59 PM Josh Reisner ***@***.***> wrote:
hm, sorry about that! we're investigating the possibility that there's an
incompatibility with certain plugins. is the page in question
https://akronaa.org/meetings/?
—
Reply to this email directly, view it on GitHub
<#1130 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A74IZQLLLHKUL7HBFCICFBLXGLUR5ANCNFSM6AAAAAAYC75L6E>
.
You are receiving this because you authored the thread.Message ID:
<code4recovery/12-step-meeting-list/repo-discussions/1130/comments/5911379
@github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
ok that's good intel, thanks! we are thinking it is a cron, and were thinking it might be either yoast or woocommerce. the other site it was happening to we rolled back to the previous version of the plugin, and should know within about an hour whether that worked or not |
Beta Was this translation helpful? Give feedback.
-
|
I also tried switching between the Legacy and TSML one of the days.
On Mon, May 15, 2023 at 11:01 PM Gregory Kennedy <
***@***.***> wrote:
… Yes. I happened to be working late tonight and had the page up about 10
pm. I noticed it lost the link around 10:20. I had wondered when it was
happening so I will take a look tomorrow to see if one of our backups is
running around that time. I tried turning off YostSEO yesterday but that
didn't work.
On Mon, May 15, 2023 at 10:59 PM Josh Reisner ***@***.***>
wrote:
> hm, sorry about that! we're investigating the possibility that there's an
> incompatibility with certain plugins. is the page in question
> https://akronaa.org/meetings/?
>
> —
> Reply to this email directly, view it on GitHub
> <#1130 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A74IZQLLLHKUL7HBFCICFBLXGLUR5ANCNFSM6AAAAAAYC75L6E>
> .
> You are receiving this because you authored the thread.Message ID:
> <code4recovery/12-step-meeting-list/repo-discussions/1130/comments/5911379
> @github.com>
>
|
Beta Was this translation helpful? Give feedback.
-
|
We use both yoast and woocommerce on the site, both are up-to-date and we
are on WordPress 6.2 right now.
…On Mon, May 15, 2023 at 11:07 PM Josh Reisner ***@***.***> wrote:
ok that's good intel, thanks! we are thinking it is a cron, and were
thinking it might be either yoast or woocommerce. the other site it was
happening to we rolled back to the previous version of the plugin, and
should know within about an hour whether that worked or not
—
Reply to this email directly, view it on GitHub
<#1130 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A74IZQIX5KETIVCX5NPTRW3XGLVQTANCNFSM6AAAAAAYC75L6E>
.
You are receiving this because you authored the thread.Message ID:
<code4recovery/12-step-meeting-list/repo-discussions/1130/comments/5911451
@github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
so our best thinking is that a change in interestingly the other site experiences the issue around the time yours does, but slightly later. ~10:40 CT we are going to release a new plugin version soon but we need to test some things. the code we're going to release is this: #1131 so to fix the issue locally one option is you could install the wp-rollback plugin, and roll back to or if you want to be adventurous you could replace the contents of |
Beta Was this translation helpful? Give feedback.
-
|
@AkronAAIT fyi |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. I installed wp-rollback and went to 3.14.13. I will see if that
helps tonight. FYI, I first tried replacing the functions file with the one
you provided and it was throwing an error in init where the custom post
types are registered.
…On Tue, May 16, 2023 at 1:01 AM Josh Reisner ***@***.***> wrote:
so our best thinking is that a change in 3.14.14 is not compatible with
one of those plugins, but we're having a hard time figuring out which.
we've tried running the crons that these plugins run and can't trigger the
issue manually
interestingly the other site experiences the issue around the time yours
does, but slightly later. ~10:40 CT
we are going to release a new plugin version soon but we need to test some
things. the code we're going to release is this: #1131
<#1131>
so to fix the issue locally one option is you could install the
wp-rollback plugin, and roll back to 3.14.13 (should not cause any
problems) and turn off automatic plugin updates (if they are on) and wait
for 3.14.15, should be out in a few days.
or if you want to be adventurous you could replace the contents of
wp-plugins/12-step-meeting-list/includes/functions.php with this file
<https://raw.githubusercontent.com/code4recovery/12-step-meeting-list/29ab40c7506a3924d09bec0631c0cecc2fc9f5e6/includes/variables.php>
—
Reply to this email directly, view it on GitHub
<#1130 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A74IZQODRXZAWXQWODNC5TTXGMCYZANCNFSM6AAAAAAYC75L6E>
.
You are receiving this because you authored the thread.Message ID:
<code4recovery/12-step-meeting-list/repo-discussions/1130/comments/5912057
@github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
did you catch what the error was? i don't see one locally |
Beta Was this translation helpful? Give feedback.
-
|
I had pasted the code in the plug-in editor. When I hit save it said there
was a fatal error on line 7 of the includes/init file so it wouldn't let me
save. There was a traceback but I didn't pay attention since I just went on
to use the rollback plugin. I suppose I could do it again if you think that
would help trace the initial problem.
…On Tue, May 16, 2023 at 9:40 AM Josh Reisner ***@***.***> wrote:
did you catch what the error was? i don't see one locally
—
Reply to this email directly, view it on GitHub
<#1130 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A74IZQJ7Y2WZT2OPVG3L6TLXGN7UTANCNFSM6AAAAAAYC75L6E>
.
You are receiving this because you authored the thread.Message ID:
<code4recovery/12-step-meeting-list/repo-discussions/1130/comments/5916745
@github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
oops, i see the problem. above i told you no need to retry, thanks. let's see if rolling back the plugin prevents the reset |
Beta Was this translation helpful? Give feedback.
@AkronAAIT fyi
3.14.15is out now and should hopefully resolve the issue for you. while we never determined the cause, deploying it to the other affected site appears to have resolved it for them