maxxd

Note that "$get_the_title()" is not the same as "get_the_title()".

And that code is exactly why I hated working with WordPress themes. Anyway, replace the 4 instances of $site_title with get_the_title() That should do the trick for you.

@requinix - I too hate the "magic" aspects of Laravel. I really don't think it should take hours to figure out where data is coming from... @gizmola - Thank you for taking the time to write all that out! I'm planning on doing some more research this weekend and will definitely keep your post in mind as I do. Admittedly I like Twig and Doctrine myself, so I'm definitely gonna take some time going through those git repositories as well.

Somehow I'd forgotten about Symfony - thanks, @kicken!

Hey y'all. I'm doing some research right now and wanted to see if anybody has personal experience or opinions they're willing to share. I'm not looking for anyone to try to tell me which is definitively the best framework. My company is looking to migrate our application to a remote RESTful API to support about a thousand (for now) installations across several continents. I've been asked to look into what we want to use to do that. The choices on the table right now are CodeIgniter 4, Lumen by Laravel, and Slim. Personally I'm leaning toward CI4 at the moment as I like the updates they've made to the framework as a whole - it actually feels like a modern framework now, it's got fairly robust functionality without being overly opinionated, and it's zippy from what I've seen. However, it doesn't come with authorization out of the box, so that'll have to be home-grown. I'm leery of Lumen because... well, fair or not, it's a Laravel product and I have some qualms with Laravel - it's the overly opinionated thing, mostly. Slim I don't know terribly well (I played with it a bit a year or so ago) - it looks nice, but seems like it's pretty much just a router and we'd have to create all the CRUD functionality and whatnot all over again. All of that being said, really nothing's off the table at the moment and I can see pros and cons for each of them. Which is why I'm asking here - any stories to share? Pain point, pleasant surprises, things you can't live without (or with)? Thanks in advance!

500 status is a server error. If you click on the error row in the Network tab in your developers tools and then click the 'Response' tab in the popout, it should show an error of some sort. Or at least some output - what does that say?

You'll need the Facebook PHP API. Once you figure it out, it's not too bad to use as I remember. Admittedly, I haven't used it in a long time, and I will say I hope the documentation has gotten better because it seriously sucked when I used it.

Quick update - this appears to get me the data I need - thank you @Barand!

I don't mean to sound like an ass by saying this, but that is adorable. With the current updates in esNext (whatever year it's on now) you can seriously cut down on the number of lines of code you have to write, but you also seriously erode the readability of the code if you're not careful. Either way, with or without a framework, kicken's code is the least amount code you can expect to write - if you want it to do anything other than announce the fact that you've clicked something, it's going to take more thought - and code - from you.

That's exactly what I was looking for out of the query - sorry for the late response, my internet connection is deeply inconsistent at the moment, because ... well, because Spectrum, apparently. But thank you so much for the help - I'll dig through your SQL tomorrow morning, apply it to my full situation and data set and let you know how it turns out. Thank you yet again, Barand!

product_inventory has an FK (product_location_id) to product_locations, which includes both the location ID and the product ID. product_locations.stock is used only for the stock at the actual time of the transaction - product_inventory is for historical inventory reports. As far as loading the data, I've got seed files if that's something that'll help - I had always gotten the idea you were more straight PHP than framework, but I'd be happy to copy and paste if it'll help.

Hi y'all. - I've been beating my forehead against this for a few hours now and though I'm sure it's something incredibly obvious and simple, I'm just not seeing the error. This is a historical inventory query - the data is as follows: product_inventory product_locations locations products OK - so that's my data setup. My query is this: SELECT p.productName ,p.productCode ,pi.current_inventory ,pi.transaction_date ,l.name FROM products p LEFT JOIN product_locations pl ON p.productCode = pl.product_id LEFT JOIN ( SELECT product_location_id ,transaction_date ,current_inventory FROM product_inventory WHERE transaction_date < '2020-01-03 23:59:59' ORDER BY transaction_date DESC LIMIT 0, 1 ) pi ON pl.id = pi.product_location_id LEFT JOIN locations l ON pl.location_id = l.id WHERE l.id = 1; And this is my result: Note that I'm not getting a value for either current_inventory or transaction_date for product S10_1949, despite there being 3 matched rows in product_inventory. Can somebody kick me in the head to knock the dust loose and help me figure this out?

Set up a listener in a JavaScript file that's included in the HTML page. How this happens depends on what JavaScript framework or library you're using - if any, because that's different, too - but basically you want to set up a general onclick() listener for your element(s); give each clickable element (the <li> elements in your case) a unique selection attribute so you know specifically which one has been clicked. You can give them all different id attributes or use data-* attributes - whatever is easiest for you works, however I recommend being consistent so as to avoid confusion in the future.

There's gotta be more info here - the log you shared doesn't indicate any kind of problem, and the image looks like a file is uploading. Post any error messages you're getting in the browser or the developer's tools (make sure you check the network tab).

No, using CSS will definitely be better at accomplishing it. You're talking about responsive web design, which is not accomplished with PHP. Stop trying to use a bazooka to kill a gnat.