This forum has moved to a new location and is in read-only mode. Please visit talk.octobercms.com to access the new location.
This morning I moved a dev site onto a staging server for clients to take a look at progress and run into some unexpected problems. The main one, and which I haven't yet resolved properly, is that all plugin components were either not showing anything or were showing the default markup.
For a couple of them it seems that the staging server is much stricter about case and I'd made some typos (although this surprised me as the Homestead/Forge setup should be using the same setup). Any clues on why it was working on one and not the other welcome.
Where it was showing a components default markup it seems that the ability to read a component replacement partial from the partials directory isn't working on the staging server.
For example I have a component called Blog. It has an alias of componentBlog. It's called using {% component 'componentBlog' %}. In the theme's partial directory is a componentBlog/default.htm file. This works fine on the dev server as expected. The same setup on the staging server doesn't work. If I change {% component 'componentBlog' %} to {% partial 'componentBlog/defult' %} it works fine*. Can anyone think of any reason why that would be?
Happy to check things as suggested and report back.
Thanks,
Adam
*by works fine mean it loads the partial - as I'm using SELF in it that bit barfs but not worried about that right now.
Last updated
Ok so apparently Vagrant on Mac inherits the native file system's approach to case sensitivity - which is insensitive - so I can make changes on my dev to be reflected on staging which will help with some of these issues.
However can't get my head around the component problem That is case sensitive so should be working. Just for info the overriding of component partials from this: https://github.com/octobercms/docs/issues/18.
Last updated
Only thing I can find that's noticeable different is php version - staging server on 5.6, vagrant on 5.5
Last updated
Ok I've ruled out php versions as updated vagrant to same and it stll works ok locally. I'm still having this problem if anyone has any ideas - components loading default views instead of replacement partials.
Ok so this was solved by deploying as per here: http://octobercms.com/forum/post/deploying-cms
No idea why install fresh OctoberCMS solved it though.
1-5 of 5