requinix

That code has a line which changes the text (according to the amount of time left). It also has a if block that does something when the countdown ends.

Any change if you lower the sleeping time(s)?

How fast does the output come? Is it 500 almost instantly or do they come in over the course of a minute? Is the script stopping "normally" because it thinks there's output or because it has some sort of problem (like a timeout)?

If there's an error then it would help to know what that error says...

Threads merged. We can try to help, but would need quite a bit more information. Like what forum software it's using. And assuming that comments were ever working, what's changed recently.

* means any element. div.font only applies to DIVs with a "font" class while .font applies to any type of element with a "font" class. # is for IDs. These are fairly basic CSS questions...

phpunit/phpunuit already provides phpunit/php-timer. Don't install it again. composer remove it, delete your vendor directory, and composer install.

I gave you the wrong name. The Composer package is phpunit/php-timer, therefore the files would be in vendor/phpunit/php-timer. Do you have them?

Try regenerating your autoload files, just in case that didn't happen properly. That class looks like it comes from sebastianbergmann/php-timer. Make sure you have that directory in your vendor/.

Did you install it with Composer?

You're not listening to me. I'm not asking you to describe what happens when you run either of these scripts. I'm asking you to actually run the URLs I'm telling you about and see what happens. Because the answer to your original question of "are there security problems here" is a very definite "yes", and I had hoped that the easiest way to tell you about it would be for you to watch it happen yourself.

Not what I'm saying. What if you go to https://www.mysite.net/ota/delete_ESP_data.php?file=delete_ESP_data.php

What's the name of your PHP file? Let's pretend it's get.php. What do you see if you go to /get.php?file=get.php

Also note that isset() accepts multiple arguments.

Variables defined outside of functions are not available inside of functions. If you didn't see PHP give you a warning about that then you probably do not have your environment set up properly for PHP development. Find your php.ini and set display_errors = on error_reporting = -1 Then restart PHP and/or your web server and try your script again.

Didn't notice this thread earlier. If you didn't see the answer elsewhere, there were problems with Elasticsearch staying alive: kernel kept killing it due to memory problems. Then a reindex or two. Everything seems fine and stable now.

Looks fine to me. Is the problem your browser?

Something about your assumption is wrong because both messages are definitely indicating that $table is not defined. You can test it really easily: define $table as an empty array before the loop and see what happens.

I get you're trying to figure this out, but using "global" variables and "variables variables" (the name for this double-$ stuff) is not a good idea. They are bad features of PHP and you should do everything you can to avoid using them.

I hate the ligatures. Especially the ≤ and triple ═══. I'd have to relearn how to scan code.

You need the value of #txtSearch at the time the button is clicked, not when the page loads. And if you're going to be putting arbitrary values into the URL then you need to use a function like encodeURIComponent for it.

Have you tried a query that lists all the columns and requires any of the conditions?

You say you don't want to use CSS, but then you do things like <div class="col-2" style="top:-15px; left:-20px;"> and <div class="col-6 text-justify" style="position: absolute;height: 68px;left: 22%;right: 27.05%;"> which is very much the opposite of that. If you are going to use Bootstrap for positioning then do not do your own positioning. Work with the system, not against it.

If you also wanted permissions on some sort of "container" then you've basically discovered the Unix permissions system. Can you say that, for each permission, "if public can do X then owner and group can" as well as "if owner can do Y then group can"? If so then you have a hierarchy-based model and your system needs only know the lowest level in the hierarchy to permit the action - the second example you have. If not then you probably have a role-based model and you'll likely end up granting individual permissions to each group - the first example. In other words, first you need to know at a high "business" level what the permissions system must be capable of supporting: how people and groups relate to each other. If it isn't clear what that needs to look like, consider looking at existing permissions systems (which are mostly hierarchy- or role-based), see which seems most appropriate, and copy it.

It's not stupid. Not by much. My version looks almost the same: opening parenthesis, capturing group, some ungreedy amount of stuff that isn't an opening or closing parenthesis (you used an assertion instead), the word "required", and the closing parenthesis. If you absolutely can't stand having a $1 group, swap the opening and closing parentheses for assertions. But this will make it look more "obtuse". If you care about squeezing every bit of performance out of this regex then we can keep going, but with short input strings I'd need a pretty darn good reason to put in the effort.