maxxd

After your initial if(isset($_POST['save_excel_data'])){ add this: die("<pre>".var_export($_FILES, true)."</pre>"); Just check and make sure you've got the data you think you've got.

Downloading the library is the first step; next is implementing it. What have you done so far? Show your code (and please use the '<>' button to paste it here in the thread).

Good point, and now that I think about it Laravel uses `.blade.php` - which, to be honest, I've always found a bit silly. Just use twig...

If the book is recommending using `.html.php` as a file extension, I'd question the quality of the book to be honest. I haven't seen a reference recommend that in... well, years I think.

The thing is, time zones seem like a simple thing until you start to run into them in code - then they turn into the actual, true, legitimate, and complete devil. I have somehow over the last three or four jobs I've had turned into the dude that fixes the time zone issues and I can say that each and every time has been a monumental pain in the ass for different reasons. It may not look like you're having a time zone issue, but as kicken has pointed out - it is. I have found https://momentjs.com a bit easier to deal with than straight JS Date(), but you still have to be cognizant of the time zone.

For my money, CSS variables (custom properties will sometimes get more hits on google) is the way to go here. Deal with any changes using Javascript, which can interact with the CSS variables directly and not have to wait for page reloads, etc. I'd recommend using php to inject the values into inline Javascript instead of inline CSS, though that's probably a weird personal thing. In my brain keeping the CSS in one place is easier to read, although I expect some inline Javascript. Like I said, it's a weird personal thing...

This is a soap response; why not use the SOAP client?

Honestly, there's nothing really complex in either file - I've got a couple other, more specific setups that I use that get a bit more into the weeds (can't share those, unfortunately, but I can talk about them if there are questions). Really the dockerfile is just setting up the server instance - installing and enabling php extensions, installing node and composer, etc. The one sorta tricky thing it does is change the default webrooot in apache. And the docker-compose just creates the server and sets up the database and mail spoofer. I've found it works just about equally well on mac and windows, so it's kinda my go-to. I'm more than happy to answer any questions on both files - either hit me up here or DM me.

If you're looking for easy onboarding and not production deployment, here's mine. I certainly won't say it's perfect, but with only a couple exceptions in the past year or so it's worked reliably for developers coming on to a project. Hope it can help some. https://bitbucket.org/maxxdesigns/docker-base/src/main/

I assume given the target attribute that you're deploying to production with this, yeah? If so I'm gonna bow out (hopefully) gracefully - I don't have enough experience with servers to guarantee the production-readiness of my base docker build. If you're just using it for dev, feel free to hit me up and I'll share - admittedly it's set up for my current Laravel environments, but it could be a useful jumping-off point.

What's your docker-compose file look like? We need to see that in order to say if it's an issue with the volume mounts.

BTW - that totally did the trick. Thanks much, @requinix!

In reality the heights of the rows can vary somewhat (the width of `right` is a known, so that'll absolutely work), but I think the content is consistent enough that I can estimate enough to make this work - thank you!

Haven't seen webpack encore before - thanks for the heads up!

Hey y'all. So, I've got a design I need to match and I'm having some issues. So far CSS grid is working exactly like I thought it would except for one small issue - I need the text in the content area to wrap under the image in the right area. It's not working using column/row assignment (I tried using shape-outside on the image; no love) so I tried grid-template-areas and grid-area. Still no love. Visual reference: what I have currently- And what I need: Here's the CSS: .container{ display: grid; grid-template-columns: 115px 60px 200px 330px; grid-template-rows: repeat(6, 100px); grid-template-areas: ". title title right" ". stats stats right" ". refs refs right" "head head cont right" "head head cont ." ". . coda ."; } .right{ grid-area: right; background-color: blue; } .title{ grid-area: title; background-color: yellow; } .stats{ grid-area: stats; background-color: red; } .ref-container{ grid-area: refs; background-color: green; } .headshot{ grid-area: head; background-color: black; color: white; } .content{ grid-area: cont; background-color: orange; } .coda{ grid-area: coda; background-color: aqua; } And HTML: <div class="container"> <div class="right">RIGHT</div> <div class="title">TITLE</div> <div class="stats">STATS</div> <div class="ref-container">REF-CONTAINER</div> <div class="headshot">HEADSHOT</div> <div class="content">CONTENT</div> <div class="coda">CODA</div> </div> I tried using this: grid-template-areas: ". title title right" ". stats stats right" ". refs refs right" "head head cont right" "head head cont cont" ". . coda ."; But apparently wrapping the cont area into a second column is invalid.

I agree setting up webpack is a slog, but IMO using laravel-mix makes it much easier; and then everything just runs in the background. Despite the name it's not actually tied to Laravel (and I agree with gizmola about Active Record and Laravel's implementation - it's not always awesome) but it kind of does walk you through some of the configuration you typically have to do manually in webpack. It also handles prefixing, minifying, uglifying, and transpiling pretty much out of the box for as much as that may be necessary to your site.

Where? You posted this: echo "<pre>"; print_r($this->Model_fleet->saverecords); This won't actually run the saverecords() method, and even if it did it's now passing no arguments instead of 15. Instead of passing all the individual properties of saverecords() to insert(), create an array of them and pass that to the db->insert() method. Before you do that, though, echo every row of the csv file to the browser to make sure your problem is with storage and not input. If the script can't find the input file it certainly won't be able to store the records to the database.

I don't see a set_flashback() on success - I also don't see you checking for success or failure on the insert; I see an else statement if $_POST['submit'] isn't set (which is kinda problematic as sometimes the button doesn't get passed along in post - I don't remember why or how, but best practice is to check the request method when processing a form) but the return value from your model method saverecords() is never checked. If insert_id() returns null or void then you can assume the insert failed. The other concern is that db->insert() takes two parameters - one string and one array - but you're passing 16 string parameters to it. That's one parameter that matches expected type, one parameter that doesn't match type, and 14 parameters that are ignored entirely.

From the documentation for db->insert: Have you tried catching the return value from the method and echoing it out during the loop? Or even just echoing the values on each loop so you know that you're dealing with what you think you're dealing with?

I kinda feel like you need to load the model and tell it to connect to the database before you try to do anything with it? I think the last time I worked with CI was like 3 years ago? It was slightly before the onset of covid, so I may be completely wrong.

It's been a few years since I used CodeIgniter, but it certainly looks like you're passing 15 parameters (one of which is a dynamic variable) to a method that accepts 2 parameters. If you try to dump anything other than $v_number or $v_reg from your save_records() method, what do you get?

I don't know what RPi-3B is and I'm not a SysAdmin but I will say the if you're starting a new project with no skin in the game, go with PDO over MySQLi. It's much easier to work with and (I think) enabled by default. (I think.) Either way, I know it's easier to deal with while coding. mysqli is not a direct corollary to the removed mysql_* functions so no matter what you're going to have to refactor a good amount of code.

Fair warning, I've not tried it but I've heard some good whispers about Rector.

What's the plugin? If it's dead there's probably an alternative that does a similar thing or a reason it's no longer supported.

Huh. I could've sworn I read somewhere that non-existent array indexes were promoted to fatal errors - I must be mistaken.