requinix

Don't presume. Check the documentation.

You're way off. For one, it's not an object. In fact you explicitly told PHP that you did not want an object. So it gave you an array. If you want an object then do what Barand said. For two, you don't seem to have any idea how the data is structured. Maybe something will click if you look at indented print_r output? Array ( [data] => Array ( [185.220.101.46] => Array ( [domains_count] => 0 [domains_list] => [updated] => 2019-12-02 22:04:25 [spam_rate] => 1 [frequency] => 6827 [frequency_time_24h] => 106 [frequency_time_1h] => 2 [network_type] => hosting [in_antispam] => 1 [in_security] => 0 [appears] => 1 [country] => DE [submitted] => 2018-01-11 20:34:37 [frequency_time_10m] => 2 [sha256] => e39d4a9be2f210d1a75ba2b5ece08a4b35e99002b03aeb6ceaad1d98de87c248 ) ) )

Another option besides passing the number is to make sure the file list is always sorted (however, just always sorted), then you can search for the filename in it to get the 'n' index.

Put it into a hidden input with the rest of the form that I assume you're using. And you think that Javascript is? Spoiler: it isn't.

Did you notice the link in my post? The one that goes to a page whose very first sentence is "Xdebug replaces PHP's var_dump() function for displaying variables"?

I didn't say you were debugging. I said you're using Xdebug.

Note to self: next time someone talks about var_dump output, ask them to post said output. Because that way it will be much easier to spot when... You are using Xdebug.

I don't see anything in your code that has to do with file sizes. Are they all in the same directory? Using any subdirectories?

There is no limit on arrays. Your problem is elsewhere.

Yes.

Also, if you submit the form and see the form data in the URL, that means it isn't being sent to the server the right way...

You should support both, because people will type the domain name without the "www", but you should enforce only one as the proper (canonical) domain. Which means redirect. So for yourself you'll want both hosts file entries, and Apache should have a configuration for both, but the non-www should redirect to the www one. You also have to make sure you never link to the non-www URL (another reason to not put the domain name in your URLs) because the redirect can mess with how stuff behaves.

Oh. And don't put the whole URL in your link. It's really unnecessary. All you need is the path portion, as in the stuff after the domain. So just /moviesite.php.

licksdev.com and www.licksdev.com are two different sites. Set up a redirect so that one of them always goes to the other. So the user (eg, you) won't get confused by the two sites.

Think. This is not a difficult question. I know you can find the answer.

Note the tracking URL for the services you want to support. Most of them use GET, some use POST, some use POST but actually support GET too. Then insert the tracking code in the right spot.

...which is why we're going down the "lax security measure" path. The lax security decision comes first. The .htaccess method is a way of implementing it.

The bot is the user. Their creators realized you're constructing predictable confirmation URLs so their bots don't have to wait for anything: submit form data, hit confirmation page, have working account. CAPTCHA, and don't use predictable confirmation URLs. You should be using some sort of random token instead.

You know, the regular user management system? You don't have to have open registration, but emails and passwords and all that.

A hardcoded username and/or password that I assume will be shared for all people who need to get in.

Not sarcasm. You only need something to share some pictures for a short while, not to secure nuclear launch codes. Log in screen doesn't care if you use a database or not. All you're doing is changing how it knows whether a login is valid. Given the lax security measures already being considered: no, not really. But personally I would probably still obfuscate it a little, like base 64-encoding. Yeah, sure.

Nah. It's not like the world will end if someone were to leak the password to 4chan or something.

1. Yes, if the fancy UI is important to you. 2. As with any other user authentication system, yes.

Bots. Use a CAPTCHA.

Do you have the rest of it built out? Because if not then I would suggest using one of the millions of existing services to do this. But an .htaccess with a username and password is a really quick way to do this. They go to the site, the browser pops up a little window asking for a username and password, they enter it, and they get in. And the browser can remember it like the login for any other website.