-
Posts
15,290 -
Joined
-
Last visited
-
Days Won
436
Everything posted by requinix
-
I think you have your cause and effect backwards. You shouldn't be starting with "I want breadcrumbs" and then deciding "I should make folders for it". You need to consider whether you want folders in the first place. Given that you're working with some kind of forum thing, you probably do. Get those folders up and working first, add breadcrumbs to your pages second.
-
Correct. Apparently you're calling checkInput() with a string instead of a phpSerial object.
-
Your breadcrumb is based on browsing history. Are you sure that's what you want? Because I really doubt it is. And if it is then you should really reconsider because that's not how they're supposed to work. Unlike the kind you hear about in stories, page breadcrumbs are not history but about location. For example, look at the breadcrumbs for this page (just above the page header): this page is located in PHP Coding Help, which is a subforum of PHP Coding, which is one of the main categories for the whole site.
-
DateIntervals have never been comparable. What has been the case was that PHP didn't prohibit it, but that meant you got the default object comparison behavior: always false.
-
Ah, there's no feeling in the world quite the same as receiving a reply that says "thank you for the advice on what I should be doing right but I really don't give a damn".
-
Sorry but I'm going to have to start with the non-relevant stuff first. 1. Exactly how many <html> tags do you think are appropriate for a webpage? Spoiler: the answer is exactly one. Refactor your code so you have less stuff in the loop. 2. Don't use IDs for HTML elements unless you actually need it. Form fields do not need them in order to work. Just names. 3. If you need a PHP function (you don't but it's not a particularly heinous crime) then don't mix it into the HTML output. Keep it somewhere easily accessible and far out of the way. Such as at the beginning of the script. Slightly more relevant, 4. Nobody uses inline event handlers (eg, onclick) anymore. That's so 1990s. If you're using jQuery then you might as well use it for its strengths - such as event handling. Find a way to set up a single event handler that will automatically apply to all of the buttons. 5. If you're using AJAX then don't bother with the <form>. It doesn't mean anything. And actually relevant, 6a. AJAX only sends the data you tell it to send. And right now, all you're telling it to send is that "call_func" thing. 6b. Your click event handler (the one you're going to write as you address problem #4) will know which button was pressed. All you have to do is get the button's value and add it to the AJAX request data.
-
Logically speaking, not all DateIntervals are comparable. Some are, depending on what they represent and how they were created. But most aren't. Consider 30D vs. 1M: sometimes they're equal, sometimes the first is less than the second, and sometimes the second is less than the first. Like kicken said, compare the intervals with respect to some relevant starting date. And I bet there will always be some relevant date you can use.
-
The only way that could possibly happen is if you gave us something to look at.
-
Elapsed Time Does Not Increment by Seconds or Minutes.
requinix replied to phreak3r's topic in PHP Coding Help
You're return;ing inside the loop. The whole function is actually kinda wrong. Try again. Without a loop. -
AJAX is asynchronous. Just because you put it in your Javascript before the .popover() does not mean it will have finished by that point. It isn't so much that it works on the second time but that by the time you mouseover again the AJAX from the first time has finished. Try it: mouseover, then out, then over, on the same element quickly. And every time you mouseover before the AJAX has completed, another one will start up. You might also be able to keep your mouse over the element and it'll eventually show. Depends on the popup code. Likely not. Render the popup HTML ahead of time instead of starting with an empty string and filling it through AJAX.
-
It's really quite simple. Object goes on the left, name of the thing you want goes on the right. https://www.php.net/manual/en/language.oop5.properties.php
-
Alter the column so that it uses a numeric data type instead of a string data type.
-
Are you familiar with objects? Seen the -> operator?
-
object(ATWS\AutotaskObjects\QueryResponse)[9] public 'queryResult' => object(ATWS\AutotaskObjects\ATWSResponse)[10] public 'EntityReturnInfoResults' => object(ATWS\AutotaskObjects\ArrayOfEntityReturnInfo)[1028] public 'EntityReturnInfo' => array (size=500) ... 1. Whatever you dumped was a QueryResponse object. 2. It has a property named "queryResult" which is a ATWSResponse. 3. It has a property named "EntityReturnInfoResults" which is an ArrayOfEntityReturnInfo object. 4. It has a property named "EntityReturnInfo" which is an array of something.
-
Not sure what you're missing yet but I can tell you what we're missing: code.
-
slider.php: SELECT * FROM haberlerekle ORDER BY haberekle_id DESC LIMIT 12 mansethaberler.php: SELECT * FROM haberlerekle ORDER BY haberekle_id
-
Laravel Error : Trying to get property 'data' of non-object
requinix replied to a topic in Frameworks
$result = json_decode($response); $students = $result->data; Whatever $response was, it was not valid JSON. Find out what it was. -
I don't think you understand me. You can write the Javascript, yes? I sure hope so because that's a rather important aspect to the problem you're describing. I'm not saying you don't write Javascript. I'm saying you don't write Javascript that tries to manipulate the element's style. I'm saying you do write Javascript that adds/removes CSS classes from some appropriate ancestor element, then handle the appearance changes with a CSS rule.
-
I don't yet understand what you want mansethaberler.php to do. You need to describe what the page is supposed show. I know that slider.php has a link and that you are clicking the link to go to mansethaberler.php, but I don't know what you want that page to do.