You have a table. The table has a primary key auto-increment numeric ID field. You want to fast-forward the ID to a certain value (which is larger than or equal to the last value the field has).
Example, let the ID of the next entered record be 1000:
ALTER TABLE `mytable` AUTO_INCREMENT = 1000;
- This simple command will give you an SVG file with QR code vector image in it:
echo "Hello world!" | qrencode --level=H --dpi=300 --type=SVG -o qr.svg
- If a bitmap is enough, just type:
echo "Hello world!" | qrencode --level=H --dpi=300 -o qr.png
- Even this simple command will work:
qrencode -o qr.png "Hi!"
- Change the color from standard black to any if you like:
echo "Hello world!" | qrencode --foreground=808080ff --level=H --dpi=300 --type=SVG -o qr.svg
- Alpha supported too:
echo "Hello world!" | qrencode --foreground=FFFF00FF --background=0000FF55 --level=H --dpi=300 -o qr.png
echo "Hello world!" | qrencode --foreground=FFFF00FF --background=0000FF55 --level=H --dpi=300 --type=SVG -o qr.svg
The data you have in MySQL is all in UTF-8, you have UTF-8 specified in your HTML, PHP is set up to use UTF-8, but you still get gibberish as output, with question marks showing up on screen instead of correct symbols.
The problem may be that the communication between MySQL and PHP is not happening in UTF-8.
Try telling “SET NAMES ‘utf8′” to MySQL when you initiate the connection, before you run any other queries.
For example, as soon as you establish the connection to database, run this in your script:
mysqli_query( $conection, “SET NAMES ‘utf8′” );
Sometimes it is enough to remove comments from your PHP code to make it not worth stealing, as a potential violator will spend more time figuring out what did you mean by all that, than writing his own version of the software to do the same job.
This very simple solution, based on an example in a forum here, does that for all files in the directory and its subdirectories.
find . -type f -name '*.php' | while read VAR; \
do mv $VAR "$VAR-old"; php -wq "$VAR-old" > $VAR ; \
unlink "$VAR-old"; done
Unlike obfuscators, it does not mess with your actual code.
The php options engaged here are:
-w Output source with stripped comments and whitespace
-q Quiet-mode. Suppress HTTP header output (CGI only).
You are serving a file for download directly from your PHP script, by setting its mime type, sending headers with Content-Type and Content-Disposition, then piping the contents.
Everything works fine, but then suddenly the downloads become corrupted, with extra data added in their top, with blank extra lines clearly visible in downloaded text files.
The first thing to do without thinking much is to go through your PHP files and remove closing “?>“, if they are at the very end of the file. They are not needed and actually can be harmful, as anything after “?>” may served to the user with potentially damaging results.
Just remove those “?>” and your downloads may be fine again.
So you write some software in PHP and are about to upload it to the server. But what if the server is not secure, what if it gets compromised, what if somebody steals your intellectual property? There may be situations where you are really concerned about it.
In most situations the best practical solution is to simply obfuscate your code, by making it unreadable to humans. It can still get stolen and used as it is, but it is very hard to practically impossible to restore the logic behind the code. And that is sufficient in most situations.
Quite good tool for that is YAK Pro. It works really well for small projects. As your project gets big and complicated, it begins to mess up the code, which makes the output unusable. But for small projects it is just fine. See for yourself, if you can make use of it.
The easiest way to install it is to use git.
1) Go to the directory where you want to have the obfuscator directory created, then type:
git clone https://github.com/pk-fr/yakpro-po.git
2) Change into the newly created directory and again type:
git clone –branch=1.x https://github.com/nikic/PHP-Parser.git
NOTE: It is “branch” with two dashes “-” before it, WordPress may mess up the text formatting.
Afterwards you may test it in action.
You may experience a weird problem, when you attempt to embed base64 encoded TTF font file in a Web page with CSS @font-face and the font just does not work. You try decompressing the base64 data, and get perfectly valid TTF file. Everything is fine, but nothing works.
Well, the problem is caused by line breaks in the base64 encoded data. It is said that those line breaks are there because once upon a time software could not handle long strings. Well, these days it is obviously the opposite. Web browsers seem unable to handle base64 data with line breaks SOMETIMES, because base64 encoded images work perfectly well even if there are the breaks. The fonts don’t though.
Whatever. Take your base64 encoded file and run this command on the command line:
tr -d "\n\r" < Font.base64 > Font-valid.base64