blanco

@BillH Thank you so much! Setting up a custom upload folder solved it! I wonder why some servers return an error when using move_uploaded_file, although its seamingly works just fine?

I should mention that the files actually seem to be uploaded when I look in the asset folder

I've been getting this error suddenly when trying to upload files. ( "Unable to move uploaded file to:..." ) The site runs fine on my local server but the live server gives me this error everytime I try to upload a file. Both servers run PHP 8.3. I have tried to change the permission of the asset folder without any luck. Has anyone else gotten this error before?

@wbmnfktr I have attached the complete list of all the entries. kommuner2.txt @a_dent I don't think so as that is not the only municipal with swedish characters ? [edit] Dude, you are probably correct! There is a "Habo kommun" in the list, I didn't even think about that! I'm gonna try and add it with a slightly different name.

I have a select option were I try to add a new value with a specific id and title and getting this error message: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'Håbo kommun-114' for key 'title' The thing is that there are no other item in the list with that id nor title. It's a list of all the counties in sweden which has specific id numbers. There are 290 of them, and all of them gets imported except one, and that is Håbo kommun with the id number 0305. I can't even see anything in the database table fieldtype_options. there is no item with that id. What could be causing this? Thanks!

I want one single pw install. But I want to have a method for just switching between two databases when developing locally. So far, the solution I mentioned above seem to do the trick. I have added this config.php: else if($domain == "sitetwo.com"){ $config->dbHost = '127.0.0.1'; $config->dbName = 'site_two'; $config->dbUser = 'root'; $config->dbPass = 'root'; $config->dbPort = '3306'; $config->paths->assets = $config->paths->site . 'assets_two/'; $config->urls->assets = $config->urls->site . 'assets_two/'; $config->paths->files = $config->paths->site . 'assets_two/files/'; $config->urls->files = $config->urls->site . 'assets_two/files/'; $config->paths->cache = $config->paths->site . 'assets_two/cache/'; $config->urls->cache = $config->urls->site . 'assets_two/cache/'; $config->paths->logs = $config->paths->site . 'assets_two/logs/'; $config->urls->logs = $config->urls->site . 'assets_two/logs/'; } $domain is just a variable that I set manually, to switch between the two databases/sites. Is this a good or bad approach?

Thanks! Option #1 doesn't really fit my needs as I will end up with two copies of the same site in different folders. I have tried another option mentioned in this thread: I just switch databases in config.php together with the config->paths->assets, and it seem to work fine. Do you see any problems with this setup?

I'm building two sites that shares the same front end, templates, modules etc. It's just the content that will differ. What is the best practice for building this locally. I'm thinking of just duplicating the database, and switch between the two in config.php. Is this practice considered good? Is there a risk of overwriting files/images when uploading? Thanks!