lorraine4
Forum Replies Created
-
Hi Michael
Could you please check if the Quick Print works with Microsoft Edge browser when you update the code?
We have had an issue using Firefox when it comes to editing our web site using the Glutenbiz theme.
Thank you again for all your help.Lorraine
Hi Michael
Subscribers are still not able to print using your program.
We get the below error codetaxonomies?context=edit { "code": "rest_cannot_view", "message": "Sorry, you are not allowed to manage terms in this taxonomy.", "data": { "status": 403Will you be able to modify your code to correct this issue?
Thank you for looking into this for us.
Lorriane
Hi Michael
Glad you are feeling better. A lot of viruses going around.
Still have an issue with the quick print for Subscribers.
Ok to print by admin and editor roles.
Here is the error message/code I get.Message when go to print “Sorry, there was a problem initializing Post/
taxonomies?context=edit { "code": "rest_cannot_view", "message": "Sorry, you are not allowed to manage terms in this taxonomy.", "data": { "status": 403 } Version Print My Blog 3.8.16Hi Michael
Great to hear that you are able to modify your code to allow subscribers the ability to print from our web site. Looking forward to the updated plugin next week!
I appreciate you taking the time to troubleshoot the problem and connecting with me.
Thank you so much!
Lorraine
Hi Michael
Our website was down for maintenance last night, but it is up and running now.
Yes, I do have Query Monitor active, but it is only viewed by admin login.
Not sure if you would see a rest error when a subscriber is online and tries to print.
Would it help if I emailed you the Query Monitor information?
LorraineHI Michael
You were correct. When I login as admin, I do not get a rest error.
When I logged in under your name as a subscriber, I received the rest error
Name
Taxonomies?context=edit
Response “code”: “rest_cannot_view”,
“message”: “Sorry, you are not allowed to manage terms in this taxonomy.”,
“data”: [“status”: 403
Is there something that can be done to bypass this problem?I have created a user login and PW for the gardencluboflondon.ca as a subscriber.
login name michaelnelson pw michaeln123.I appreciate you taking the time to trouble shoot this for us
Lorraine
Hi Mike
I updated your plugin a couple of weeks ago to V3.18.3
My PHP version is 7.4.32
WP version is 6.03Hi Mike
If I can use Quick Print when I am logged in as an editor or Admin the REST API must be enabled.
When I switch to a Subscriber login cannot initialize the Quick Print. Could the REST API get disabled when I switch to a subscriber login?Not sure how to check it is enabled when I log in as a subscriber.
I have activated Query Monitor – would it show up there?
Our site is hosted by hostgator.com and we use SiteLock SecureStarter for security.Thank you for your help!
Lorraine
Hi Mike
I am with the Garden Club of London, and we use your plug option Quick Print on our Word Press web site. It is a great plugin and easy for our members to use.
With one of the updates, we are finding members who have a subscriber role can no longer initialize a post/page to print.
If you have an assigned role as Admin or Editor, the post will initialize and allow us to print the post.
Is there a code you could add that will allow regular subscribes to use the Quick Print option of your plugin?
Thank you so much
Lorraine
Blank page when editing a creating a post – no error codes
Our website has just updated to WordPress 5.8.1 running Gutenbiz theme.
We are now getting a blank page when we go to edit/create a page or post.
This is occurring on our Windows 10 computers, iPad and iPhone.
Our editors with MacBook do not seem to have this issue.I have cleared the cache, tried 5 different current browsers, deactivated our plugins one at a time and checked if the issue was resolved after each. NO we still have a blank page occurring when we go to edit or create a page/post.
Everything was fine until we updated to WordPress 5.8.1.
Can a updated version of WordPress be sent out to correct this issue.When I did an internet search this is a big issue with many who have updated to the WP5.8.1.
I have read your responses that it is usually a plugin /browser/cache issue/conflict but we all use different plugins.
It is easier for all of us if you can correct the WP coding from your end that started these problems.
I am not a great coder so step by step instructions would be appreciated in layman’s terms.Thank you