Thread Starter
jbmaca
(@jbmaca)
To elaborate, the problem only appears to be happening with drafts. If I go to an already published post and click “Preview Changes”, it works. FYI.
This is actually something that was on the old plugin and carried over on the new plugin: From the notes on the main page:
PLEASE NOTE: A new page or post needs to be Published in order for Page/Post redirect to happen for Individual Redirects (existing page is not necessary for Quick Redirects). It WILL work on a DRAFT Status Post/Page ONLY, and I mean ONLY, if the Post/Page has FIRST been Published and the re-saved as a Draft. This does not apply to Quick Redirects.
Thread Starter
jbmaca
(@jbmaca)
The problem I’m speaking of doesn’t happen with the original version of the plugin though. I’ve deactivated your updated version and reinstalled the original version and the problem is resolved. I’m able to view previews on drafts.
The issue I’m experiencing doesn’t have anything to do with redirecting. Something about your updated version is preventing me from seeing previews on drafts. I’m getting the error I described above. FYI.
@jbmaca, just realized I should explain why this is happening. Sorry about missing this in my post above.
When you save a post or a page as a draft, WordPress doesn’t actually create its permanent link to that page or post. When you go to preview it, WordPress is literally using a temporary URL/link for you to preview the post, whereas the redirect plugin is 100% reliant on a permanent link being placed.
Once your post/page has been published (even if it’s reverted back to draft status afterward), the permanent link is bound to that page or post, which means the redirect will work properly. 🙂
Hope this helps clarify why you got a 500 error on the draft side (before publishing it). 😀
Can you do me a favor, please? Deactivate the new plugin, reactivate the old one, then go do a new post, but don’t publish it. Get the redirect link situated just as you did with the recent one, and then preview it. See if you get the error there (you should). Make sure you’re doing this with a new post or page, not one that’s already drafted/saved/published.
Thanks!
Thread Starter
jbmaca
(@jbmaca)
Thanks for the explanation Doug. I don’t understand why the issue wasn’t happening with the original version of the plugin though.
Thread Starter
jbmaca
(@jbmaca)
Sorry Doug, but I think you missed the message I posted before your last one. I’ve reverted to the original version of the plugin and the problem doesn’t happen. I’m able to view previews on drafts (haven’t been published). I don’t get the same error.
The only actual changes I’ve made are all centered around HTML coding, and not the PHP or redirect coding itself, except for one enhancement (centered around clearing caches)
I’ll see if I can replicate the issue on my side and try to track it down. Just a little perplexed, since I know I didn’t touch that part of the coding.
Thread Starter
jbmaca
(@jbmaca)
If it helps, this is what I’m seeing. On the original version of the plugin, clicking preview on a draft opens a window with this URL:
https://mydomain/wp-admin/post.php
which quickly goes to this:
https://mydomain/?p=80372&preview=true
But on your updated version, it seems to get stuck on this URL:
https://mydomain/wp-admin/post.php
before giving me that error page. It doesn’t proceed to the preview URL.
-
This reply was modified 8 years ago by
jbmaca.
-
This reply was modified 8 years ago by jbmaca.
Thread Starter
jbmaca
(@jbmaca)
Hi Doug, sorry to bother you about this, but I was wondering if I could follow this up.
I’m still having the same issues as described above. Clicking “preview” or “save draft” takes me to an HTTP ERROR 500 page.
What you mentioned above regarding the enhancement with clearing caches may be the reason in my case.
Would it be possible to send me the original code (before your enhancement) to see if that resolves the issue? Many thanks for your time.
My apologies for not responding sooner.
Did you try the change I suggested in this thread:
https://ww.wp.xz.cn/support/topic/fatal-error-2903/
That whole section is about the only new thing I’ve added into this update.
If you can do that quick adjustment and test it out, I’ll get this pushed out today.
Thread Starter
jbmaca
(@jbmaca)
No worries Doug. I did the change as you suggested and it worked! Thank you!
EXCELLENT! I’m so glad that’s all it was. Let me package this up and do a quick update now.
Got 1.0.1 pushed out just now. Thank you for working with me on this, @jbmaca!
Make sure you update to 1.0.1, since I’ve actually done some additional adjustment on the code I had you tweak. 🙂
Thread Starter
jbmaca
(@jbmaca)
Will do Doug. Many thanks as well!
