Hi Guys,
An unusual one for me, I am using Pro to redevelop an existing site (on a dev copy). it is on a VPS that I do not control or set up.
The problem is that the header builder will not allow me to create a new header to edit and gives me the error message
“Hey! unable to create new header.”
I’ll give login details & url in a private message below
Any help gratefully received
PS the client’s set up is in Dutch so auto translates to English for me. not sure if that is relevant
Hi there,
Would you please kindly increase the memory limit of the Wordpress on your installation? Please kindly read this article to know how to do so.
Also, you may need to contact the VPS owner and ask them to increase the PHP memory limit on their side.
Another point is the version of the Pro you are using. Kindly update the theme to version 1.1.1.
Thank you.
Hi, I believe all that has been done and still not working
I see the issue. This might be beyond just memory or server performance. It could be related to your server settings. Pro was built to work in standard setups. Regretfully, we could not support non-standard server configurations.
Thank you for understanding.
you see the issue?
Can you at least tell me what the issue is then?
I mean I see that you can’t edit the header. This is unusual. Here’s the error message.
AdapterError
description
:
undefined
errors
:
Array(1)
0
:
{status: 404, title: "message"}
length
:
1
__proto__
:
Array(0)
fileName
:
undefined
isAdapterError
:
true
lineNumber
:
undefined
message
:
"Ember Data Request undefined undefined returned a 404↵Payload (Empty Content-Type)↵[object Object]"
name
:
"Error"
number
:
undefined
stack
:
"Error: Ember Data Request undefined undefined returned a 404↵Payload (Empty Content-Type)↵[object Object]↵ at AdapterError.EmberError (https://dev.ahrenstravel.nl/login/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs-vendor.js?ver=2.0.6:19419:21)↵ at AdapterError (https://dev.ahrenstravel.nl/login/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs-vendor.js?ver=2.0.6:146527:16)↵ at Class.handleResponse (https://dev.ahrenstravel.nl/login/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs-vendor.js?ver=2.0.6:147806:14)↵ at https://dev.ahrenstravel.nl/login/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs.js?ver=2.0.6:52:32↵ at tryCatch (https://dev.ahrenstravel.nl/login/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs-vendor.js?ver=2.0.6:51257:14)↵ at invokeCallback (https://dev.ahrenstravel.nl/login/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs-vendor.js?ver=2.0.6:51272:15)↵ at publish (https://dev.ahrenstravel.nl/login/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs-vendor.js?ver=2.0.6:51240:9)↵ at https://dev.ahrenstravel.nl/login/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs-vendor.js?ver=2.0.6:40723:16↵ at invoke (https://dev.ahrenstravel.nl/login/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs-vendor.js?ver=2.0.6:1331:16)↵ at Queue.flush (https://dev.ahrenstravel.nl/login/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs-vendor.js?ver=2.0.6:1395:11)"
__ember1503506131802
:
"ember1354"
__proto__
:
Error
Here are other things you could try:
Ensure there are no server side caching in place (Varnish, Object Cache etc).
Test for a plugin conflict. You can do this by deactivating all third party plugins, and seeing if the problem remains. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time.
Remove custom CSS, Javascript and templates.
If those doesn’t help, it could really be related to server configuration. Regretfully, I could not pinpoint what’s causing it.
Thanks.
Hi,
I’m having trouble with this too. I have just set up a completely fresh wordpress and transferred all the relevant database tables (just the comments, posts and terms/taxonomies) and now I’m having this issue.
I have checked that I am on php 7.1
I have checked that there are no conflicts with plugins
I have removed all js and custom css
I have tried using the standard theme (i.e. not my child theme)
I have tried running it on multiple browsers?
Why is this happening?
Hello There,
Thanks for updating this thread. There are several reasons why this could happen. It could be because of security restrictions in your host server, file permissions, or maybe invalid site settings. To assist you better with this issue, would you mind providing us the url of your site with login credentials so we can take a closer look? Once you have provided us with your URL, we will be happy to assist you with everything.
To do this, you can create a secure note with the following info:
– Link to your site
– WordPress Admin username / password
Thank you.
Any luck, man? I think I’m having the same issue…
@smenavto, please start a new thread and provide your site’s URL and login credentials in a secure note. I assume that you did the suggestion on this thread 
Maybe it’s different in your case, errors could be different from each setup depending on its environment.
Thanks!
Mike, I think the reason Themeco asked you to start a new thread is so that I would not be able to read your secure note… just saying
in answer to your question, it appeared to be a set up issue on the vps. my client deleted the instance and created another and it all worked perfectly
Thank you so much for letting me know – I was under the impression only their staff could read secure notes… Lesson learned!
Could you please tell me what you mean by instance? Did your client terminate their VPS?
Thanks again!
My client deleted the wordpress application & associated folder and set it up again. I suspect that they had created the error in privileges the first time around
Right on. Thank you again!
Hi there,
Thank you @scotbaston for mentioning the Secure Note concern to @smenavto . That is correct, the Secure Note will be visible to the original poster of a thread and our staff. So as the original poster is @scotbaston whatever @smenavto adds in the Secure Note will be visible for him.
Another reason is the clarity. Totally understands that the case seems to be identical but the cases may differ depending on the environment. That is why we strongly suggest to customers to open up separate threads so that we can dig deep in each case. And at last, it will give a better way to have each case separated so other customers will have the easier time to find the information they want via search.
Thank you, both.