codesmithsf

Ah thanks, I had disabled plugins but not the theme. My theme defers javascript loading. This line that gets added to the page’s HEAD section should check if jQuery is available before trying to execute it.

jQuery(function(jQuery){jQuery.datepicker.setDefaults({“closeText”:”Close”,”currentText”:”Today”,”monthNames”:[“January”,”February”,”March”,”April”,”May”,”June”,”July”,”August”,”September”,”October”,”November”,”December”],”monthNamesShort”:[“Jan”,”Feb”,”Mar”,”Apr”,”May”,”Jun”,”Jul”,”Aug”,”Sep”,”Oct”,”Nov”,”Dec”],”nextText”:”Next”,”prevText”:”Previous”,”dayNames”:[“Sunday”,”Monday”,”Tuesday”,”Wednesday”,”Thursday”,”Friday”,”Saturday”],”dayNamesShort”:[“Sun”,”Mon”,”Tue”,”Wed”,”Thu”,”Fri”,”Sat”],”dayNamesMin”:[“S”,”M”,”T”,”W”,”T”,”F”,”S”],”dateFormat”:”MM d, yy”,”firstDay”:0,”isRTL”:false});});

And why is this loading on every page and not just the Events Manager related pages?

Thanks for the quick reply. Actually I don’t want the Author replaced. But I see that I have to check the “Disable Replace Author” box *and* select an “Assigned Author” – checking the box did the trick. Thanks!

• This reply was modified 3 years, 4 months ago by codesmithsf.

Oh never mind – looks like breadcrumbs are a custom function in the theme files so would need to modify there.

@anevins – I enabled debug mode but it didn’t seem to do anything. No errors were displayed to the screen. Perhaps Godaddy overrides it somehow.

@madhivanan – this is Godaddy’s Managed WordPress plan – there’s no cpanel access.

No, I cannot access them myself.

https://www.godaddy.com/community/Using-WordPress/HTTP-Access-Logs/td-p/38774

• This reply was modified 5 years, 11 months ago by codesmithsf.

I tried pushing the Godaddy support person I was online chatting with but they were steadfast with their:

“Sorry I don’t have access to the shared servers. We need root login to access the logs.”

I tried to escalate but no go. So ridiculous – no one should be using that model of server hosting – customer or provider. ?? This was for their “Managed WordPress” hosting plan. Customer support said customers can only access logs on VPS or dedicated server plans.

• This reply was modified 5 years, 11 months ago by codesmithsf.

Here it is for the autosave call that works. General:

Request URL: https://mydomain.com/wp-json/wp/v2/pages/440/autosaves?_locale=user
Request Method: POST
Status Code: 200 
Remote Address: my.ip.addr:443
Referrer Policy: strict-origin-when-cross-origin

Response Headers:

access-control-allow-credentials: true
access-control-allow-headers: Authorization, Content-Type
access-control-allow-methods: OPTIONS, GET, POST, PUT, PATCH, DELETE
access-control-allow-origin: https://mydomain.com
access-control-expose-headers: X-WP-Total, X-WP-TotalPages
age: 2
allow: GET, POST
cache-control: no-cache, must-revalidate, max-age=0
content-security-policy: upgrade-insecure-requests;
content-type: application/json; charset=UTF-8
date: Tue, 18 Dec 2018 22:17:37 GMT
expires: Wed, 11 Jan 1984 05:00:00 GMT
link: <https://mydomain.com/wp-json/>; rel="https://api.w.org/"
server: nginx
status: 200
strict-transport-security: max-age=300
vary: Origin
via: http/1.1 obfustacated.secureserver.net (ApacheTrafficServer/7.1.2 [uSc sSf pSeN:tOc  i p sS])
x-content-type-options: nosniff
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-port: port_10645
x-robots-tag: noindex
x-sucuri-id: 11018
x-wp-nonce: 20464aac7b
x-xss-protection: 1; mode=block

When I click the Save Draft button I see in the General section:

Request URL: https://mydomain.com/wp-json/wp/v2/pages/440?_locale=user
Request Method: POST
Status Code: 403 
Remote Address: my.ip.addr:443
Referrer Policy: strict-origin-when-cross-origin

In the Response Headers section:

content-security-policy: upgrade-insecure-requests;
content-type: text/html
date: Tue, 18 Dec 2018 22:17:26 GMT
server: nginx
status: 403
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-sucuri-block: PTA158
x-sucuri-id: 11018
x-xss-protection: 1; mode=block

Ok – I clicked on the Troubleshooting tab and clicked the “Enable Troubleshooting Mode” button. I then went to Pages – Add New. In the Gutenberg editor I entered a Title and then text in the “body” area below. Clicked “Save Draft” and get a red bar with “Updating failed” text.

BUT when I went back to the list of Pages and I see the post listed there. I edited the new page again, made some changes, and then waited. The page “auto-saved” and I see a greyed out “Saved” in the upper right. Went back to all pages and see the changes I made. So saving does seem like it worked despite the error messages.

I went back to Health check and disabled Troubleshooting mode. Went through the same process – got error messages when trying to manually “Save Draft” yet when I got back to the list of pages I see my changes.

I tried to Publish the page. Get a red bar and “Publishing failed” message. I went back to the list of all pages. The page is still in draft mode.

Hope this helps!

Installed Health Check. Not intuitive to find where it provides info. (It’s under the Dashboard menu on the left side.) For the REST API:

REST API availability The REST API is available.

• This reply was modified 5 years, 11 months ago by codesmithsf.

Moving to PHP 7.2 made no difference. Still had the same errors when saving content in Gutenberg.

And, for the record, it’s super lame that there isn’t more of a heads up in the release log or some other notification that doing this upgrade will *break functionality* of your website. I know it’s a free plugin and I appreciate the work and I know that WordPress’s workflow is bad in general when it comes to plugin updates but… I still have to say it.

Another issue was that while testing we were never getting the ability to prove that the tester *wasn’t* a spammer. We’d just get a generic error message and “please try again later” and no way to submit the form.

@jdembowski – if we’re all having the same problem, why open different topics about it. Seems like it would be better just to have one thread that helps with the specific issue, instead of scores of the same issue.

This error caught me too. It’s an issue with the “The Events Calendar PRO” plugin. tribe_get_custom_field() is a deprecated function and was recently removed. The function call needs to be updated. See

https://theeventscalendar.com/function/tribe_get_custom_fields/

A likely spot to look for this in a custom Events template file, usually in a child theme.

• This reply was modified 6 years, 2 months ago by codesmithsf.