error on fresh install

pop up error

I have done a fresh install, as normal i use the preferred .HTACCESS file instead of the standard one. I normally get 2 SHUOSIN errors but assume this is a host limitation as i increase the values within the preferred file.

My problem this time is running the set up wizard. I proceeded as normal but this time i got the following error.

It has also left the admin page looking like this.



I havnt touched any files on this installation as it was a fresh one. Any ideas how to fix this? I had hoped to alter some of the look tonight, but i wont proceed until this is sorted. I am half way through the set up wizard.

Although i might try on another TLD and install a clean install, i am using the new version BTW.
 
Thanks in Advance

 

That suggests to me the cache is not populating properly. I'd have to have a look on the install to know more clearly though, could be some kind of disk space or quota issue for example.

You can drop me an email with access and I'd be happy to take a look.

Chris Graham said

That suggests to me the cache is not populating properly. I'd have to have a look on the install to know more clearly though, could be some kind of disk space or quota issue for example.

You can drop me an email with access and I'd be happy to take a look.

From “Post #1,430”, 29th December 2016, 10:23 pm

thats interesting Chris, there isnt meant to be a disk quota on the package i have. As i hadnt done much to it yet, i will reinstall with RC28? and try again, if i get the same issue then i will email you.

They have a file quota on me but i am only at 500,000 files so plenty room left . I might just clear the cash and mess a bit first . Its been one of those days, so it might just be a bad day,,,,,,,,,,

Well you know, I'm actually happier to look at it when it is known to be failing, I might learn something. Definitely don't want other people to get random failures, even if it is some weird situation on a server.

Ok Chris, i didnt think of that! What do you need? admin login details or FTP? OR both lol

Either/both, what you're happy to provide. If you send within the next 10 mins I'll look this evening.

As always Chris, takes you 3 mins to do what takes me erm........................days! What did i do wrong? so i can avoid in future?

I just emptied the Template cache, as at least one file in there was blank. I'm not sure if it's a quota issue, a filesystem latency issue, or some kind of concurrency problem. Currently investigating.

I might need another host package, it is meant to be a testing server, i am hammering it lately. Extra Kudos for copying a theme with a meaningful name as well lol, I havnt forgotten i owe you owe you an email.

Waiting to hear back on something.

I cant see how you switch themes! I read the help file but cant find the setting it says in my profile??

There's only an option in your profile if you've set a zone to use a configurable theme. By default we don't do this as it's over-complex, we just assign themes directly to zones. So to change the theme edit the zone's to use it. I think there's also an option you edit a theme to assign to all public zones.

Ah ok, i see what you mean. That makes life a bit easier thanks

lg11 said

I might need another host package, it is meant to be a testing server, i am hammering it lately. Extra Kudos for copying a theme with a meaningful name as well lol, I havnt forgotten i owe you owe you an email.

Waiting to hear back on something.

From “Post #1,438”, 29th December 2016, 11:16 pm

Ok so it seems to be that file locking isn't working on the server. I wrote a test script that keeps writing to a file, using locks, and another that reads it, and it always stumbles on that. Works fine on my machine, and should work fine. So this is your problem. I'm going to think about it some more.

I wasn't able to identify the exact nature of your home directory filesystem. Wouldn't hurt to ask the web host that. For example, it might be some kind of network file system that doesn't support locks.

Ok Chris thanks, I will ask them but i got a feeling they wont do anything about it….. Could this be why i often get trouble changing file permissions?

The problem with the host provider (name cheap), you start with a tech support that know less than even I do, trying to get it escalated is a nightmare.

I might try the other host, it isnt as large a package but i should have room to add-on a domain and try it. These latest Domains were not supposed to be anything to do with me! But its become a money raiser for the project.

As soon as i get a chance i will email you fully, there is an interesting development which is why i am doing these mock ups.

Actually I may be wrong on it. I ran another test with a tweak to my code, and locking worked fine. So I think my test was broken, but it worked on my machine either because MacOS is handling the locking differently or because my SSD is very fast.
However, the actual Composr code doesn't have the issue my test code has, so I'm thinking more about it.

Will consider this again soon. It may have been some random one-off thing saving into the cache, but I want to do my best to reproduce, because random one-off things should not happen .

It happened again, same server, i change the theme to get around it. My gut feeling Chris is the server setup, they have changed a few things but wont tell me what. I get problems with other packages as well.

In the docs on the site it mentions no_minify=1 in the URL, i have done this and now i am using the admin editor for changing the files, its working fine, i need to work out how to change colours though, commenting out the wizard stuff seems to break things for me. This could be a basic lack of knowledge of how CSS works though.

lg11 said

In the docs on the site it mentions no_minify=1 in the URL, i have done this and now i am using the admin editor for changing the files, its working fine, i need to work out how to change colours though, commenting out the wizard stuff seems to break things for me. This could be a basic lack of knowledge of how CSS works though.

From “Post #1,464”, 31st December 2016, 3:40 pm

Maybe using the wrong types of comments?

In CSS you need to comment with /*...*/. Comments like //... won't work.

Anyway, you can just replace the Theme Wizard colour references with normal CSS colours if that's what you want.

I've decided I'm going to update all the code that writes out to files because right now we have all kinds of locking and "did it complete" checks that are basically copy&pasted throughout the code, as it's evolved to try and be more robust in corner cases like lack of disk space or concurrency. I'll write a new function that does a lot more checking, then hopefully (fingers crossed) this will resolve it.