-
Notifications
You must be signed in to change notification settings - Fork 50
example multiple-content-types not work with 404 error #83
Comments
Hi team, |
Thanks for reporting this! @alidcastano can you add the project to Appveyor so we can have tested windows builds ? |
@medfreeman I had the same error on CentOS with |
@STnetwork thanks, i mixed up different testing sessions, and i encountered the same one while running the example on Ubuntu. |
@medfreeman , any update for this critical issue , It totally not worked for nuxtent project. |
@alterhu2020 the warnings have now disappeared with the latest commit, they were related to an old Concerning your error, can you try with the updated examples ? If it doesn't resolve your problem, |
@medfreeman for me it's resolved with But ! You should see the process generate, is it normal to have At the end he doesn't generate all files in the multiple-content example because of this. I think it's because you replaced |
Hi @medfreeman , yes when use the latest |
@alterhu2020 @medfreeman |
Why are you visiting What does |
@STnetwork Thanks for looking into this. It works for me as well so this most be an env specific issue. But I did experience two other issues #88 #89 so we will work to fix them. Thanks for being patient as we work out the kinks, and a special shoutout to @medfreeman for helping to stabilize nuxtent. |
@medfreeman I am fairly new to this but I get hundreds of warnings: |
Environment
OS Version: Windows 7 Enterprise SP1
NodeJS: 8.5.0
NPM: 5.4.2
Nuxt: latest
Nuxtent-module: latest (1.0.0)
Hi team,
It's too sad that I had to say that the example in you official repository still not work for you current latest release version.
Steps to reproduce
npm install
npm run dev
See all my posts
Actual Result
I think it caused by incorrect axios's baseURL setting. could you try it in your side?
thanks.
The text was updated successfully, but these errors were encountered: