-
Posts
895 -
Joined
-
Last visited
-
Days Won
1
Everything posted by phppup
-
What would be the car, in this instance? jQuery? The car has obvious advantages. (although there are far less deaths from buggy incidents per capita, so is the trade off worth it?) Not trying to be a smarty, but if you are referring to jQuery, I don't find it as straight forward as JS, so unless I'm missing some great advantage, I think I have enough troubles already. LOL As always, your insight and guidance are appreciated.
-
It seems effective and it's what I'm accustom to. What is the new fangled option? Why use it other than to be more fashionable?
-
If my form is submitted, but fails during PHP validation, then I want info that was already submitted to be available. <input type="text" name="username" value="<?php if(isset($_POST['username'];} { echo $username; } ?> > </div> This works fine and defines my goal. My troubles arose when I attempted a similar design with a drop-down menu. Making matters worse, that menu uses JavaScript. <script> document.write("<select name='menu'>"); for(i = 1; i < 20; i++) { document.write("<option value=' "+i+"'> " + i + "</options>"); } document.write("</select>"); </script> I've begun trying to add PHP into the <option> tag, but am not sure how (or if it's acceptable) to integrate the JS for the desired result. document.write("<option value=' "+i+"' <? if($_POST['menu'] == ?> +i+ <? echo selected";?> > " + i + "</options>"); I suppose I could swap the JS with PHP, but then I put unnecessary usage to the server. Best solution??
-
OR perhaps I should take a different approach: I have a checkbox that controls a toggled effect on HTML background. var chosen = document.getElementById("XYZ4").checked; I'm considering adding a second checkbox that would have the same effect. Rather than hardcode both (and future) checkboxes, what would be the best way to retrieve an identifier so that it can be inserted as a variable and used to evaluate a condition?
-
My very first entry on this topic was I believe my initial effort was document.getElementById("+XYZ4+").checked; That's what necessitated the post. But I can try it again, I suppose.
-
I just KNEW you were going to do that. LOL. However, I'm not sure it's accurate (as if you need something to keep you busy) because if the 19 is on Sunday, the holiday would be Monday. [minus 2 changed to plus 1 ??] Care to enlighten me?
-
There's ALWAYS more code. But it's mostly HTML or unrelated. Essentially, I'm running through all the input tags and then separating those that are checkboxes. Then, I'm grabbing the ID of the checkboxes and using them [actually only one for now. ie:XYZ4] to "do stuff" depending on whether or not the box is checked. (I'd tell you what happens further down the line, but I haven't coded that far ahead yet. I was testing the waters as I progressed and stopped when I discovered this odd circumstance. However, my notion is to alter color or display a message if checked.) Again, it works when hardcoded and the number of checkboxes is minimal. But it would be nice to be able to have the code effective with each checkbox being evaluated through the 'for loop' (unless there's a better way to accomplish this).
-
Signed into law yesterday to commemorate June 19, but recognized on the weekday closest to the 19th when 19 falls on the weekend. (This would be interesting to code. LOL) What kind of "observance" could there be if government workers weren't "entitled" to another day off from work (with pay)??
-
Ummm, back to my original posted question, maybe, please. PS: toolbar looks awesome.
-
@Barand didn't know that. I'll try it next time. Easier than twisting the phone sideways too. Overall, code has been less problematic (except for this anomaly). Hope things have been well with you. New "official" holiday today: Juneteenth. No other news to report.
-
@Barand I do. Maybe my screen just isn't big enough, but that's how I get the quote option.
-
I would if I could. But when I access from my very very smart phone, the quote is the only available option that resembles <>
-
RE-POSTED for clarity and errors ** Ignore the TWO previous similar postings ** It originates from in the beginning of a FOR loop and I then rename it to use within the same loop. At it's inception And I expected dee to work as described. What exactly is a "proper variable"? What would make it improper? Note: when posting code that contained [ ] and lowercase i the code showed incorrectly and altered text to ITALIC. Mgmt may want to address this.
-
My problem amounts to tryong to get element using a variable's value instead of a hardcoded name. This works But this has been problematic I've tried an exhaustive array of variations with single quotes, double quotes, and + sign combinations, but seem to be missing the bullseye. How can I insert the variable so that var chosen is viable?
-
I stayed surfing the web again (someone should unplug that thing) and went down the rabbit hole, again. The code above displays lines of character text. Uncommenting the two header lines created a black screen with a black outlined square. How can I get a the image to display? Can I use this method to display multiple images? Will this provide a layer of security by eliminating a visible url to the image?
-
Either the code or it's creator needs to take a nap. I get cranky when I'm hungry. Empathetically, I accessed some code this afternoon that had worked fine 2 months ago. But this afternoon it was obstinate about running. It took 3 hours before I discovered that TWO conditional statements had been removed with comment tags. That darn code must've gotten active after I tucked it in and turned out the light. There's no other rational explanation. Pleasant dreams.
-
You need to understand what your code is saying. The first version says: attempt this, attemp that, try to send mail, try going to the Thank You page. There are no indications or notifications of which success and which fail. The alternate version directs the process to EITHER go to the Thank You on success, or indicate failure. It's safe to safe the email is FAILING in all attempts. You just don't restrict it from going to the Thank You page on the first version. I would hardcode and see where that takes me. Also don't forget my initial statements about spam filters. I'm not familiar with PHPmailer, but it could be beneficial.
-
@kicken Using file_get_contents($image) gave me a page with characters and LOTS of black diamond-question marks. That's what got me into this mess, and lead me down a path that had suggestions on the WWW to use everything from decode_base64/encode_base64 to bin2hex etc. I think all my images are now inverted, upside-down, and mixed between Latin, Arabic, and Japanese characters. LOL It seemed like a good idea at the start. Maybe I'll just back away from the path verrrry slowly.
-
If you put the first few words of a notification into a search engine, you can generally begin to find an understanding (and hopefully a solution). The last item of the message that provides "line #" is referencing the line in your CODE where the error occurred. (Taking into account that sometimes the error existed but didn't cause a problem until this point, the line number is accurate.) Depending on your code editor, the line numbers are available, although counting to line 21 isn't nearly as difficult as finding line 642. LOL. (an empty line is still a counted line) Make sure to eliminate the error initiation code BEFORE going live. It gives too much information to a user if displayed at an inopportune time. I'll take another look at your code, but beyond this point, there are other people here that would be more capable than myself.
-
Do you want this?? print_r($array_name);
-
As previously mentioned, YES, place some functional validation to determine IF the system sent the email. Something like This will not only help you during development, but also benefit the user when operational. And, as often recommended, turn on ERROR REPORTING by placing this immediately after your opening PHP tag <? (if you haven't used this, just do something blatantly wrong and then run the page to see the result) ** Remove it BEFORE production ** Aside from your CODE, other variables can be in-play with email. Spam filters are notorious for creating issues. If you're sending and receiving identical messages repeatedly, the safety net may outsmart itself and cause you an issue. I've personally had emails take hours until being released by the server. Or tested soooo many times that a failure/spam designation stopped everything. My suggestion: if the code is good, send an email to an outside address and confirm it to another (with a subject line that does NOT contain "test" or "sample" etc). - EVERYTHING has to 'appear' to be "real/valid" communication. Once you've established that messages are being sent and received adequately, then you can gingerly tweak the settings (with a degree of confidence).