schulius

Thanks for looking! - I had indeed managed to get it working when I realised that the reason for "only logo" was that all *modules* were not activated yet - I guess this had not quite worked during the installation routine (strangely there was a success message for having installed the modules). When I realised, that it was to do with modules not being activated I ran the installer (/install) once more and I think I had made the modules dir 777 for that and then all the modules did get activated! Sorry that I only got round to writing this down now. So for other users in future who have the same problem of only the logo displaying: check if any modules are activated in the back office (/admin).

Hi, I'm properly online again now. If somebody could have a look at this and would have an idea why the templates just seem to render empty stuff whereas if you go to the mobile version it seems to work - it would be great to get ideas as to why this is happening - maybe some permissions issues with some template folders or so? though seems to all be like it should... Thanks! http://nctest.natur-co.de/index.php

Thanks Benjamin, So my admin section seems to have fixed itself. I will check the storefront for missing files but it seems that the templates are simply rendered empty. (The mobile version works btw. Renders all the sample products etc. am currently on a phone but will post more detail when on desktop again...

This fixed itself strangely enought. What isn't fixed is that the main storefront is empty apart from the main logo(seems not a CSS issue, the Dom elements are all empty..). It was a fresh install.

Hi, has anybody had the same issue: My shop's admin looks so broken I cannot use it properly after having installed it... (same for the shop front but I think there it makes sense because it is probably still set to my old theme somehow (tried to change that in the admin but as I can't operate admin that is difficult)). Screenshot attached.

Hi, I got it to work after all - I think what solved it for me was to give "/translations" a chmod 777, Hope this helps others...

Hi, I got it to work after all - I think what solved it for me was to give "/translations" a chmod 777, Hope this helps others...

does anybody have a solution for this - seems like quite a few people have this issue but have not found a solution yet... thanks

Hi, had exactly the same problem - the solution above did not work for me - any other suggestions?