Category: wpHakka Threads

que me ignoraram, não ajudaram, não ofereceram serviço, especialemente aqueles que odeiam competência e vivem boicotando e inventando histórias cabulosas …

sem essa ajuda fundamental, que garantiu sossego total para desenvolver, nunca teria conseguido desenvolver o meu mais novo projeto Metro Framework para construir websites baseados em wordpress em tempo recorde e com segurança total que ninguém consegue invadir ou roubar conteúdo

uma obra mestre inédita, não existe semelhante, de

zfbsd/PROGS/Metro_Underground> wc -l ./*/*

134235 linhas total

escrito a mão própria , bug-free, error-free, instalar e esquecer …

Obrigado a todos que participaram na sabotagem!

:) peace!

you never wanted to trash wordpress for that stupid functions.php?

that can be true only if you never used it …

but when, it doesn’t take long to hate it, but hate it more than anything else, who invented that thing, or better, why they never fixed it?

theme makers are just like any other average user, they just let it be, let the charge come down on you …

this madeness that it can be overwritten, expunged or have errors causing a fatal error which crashes your site, while at the same time it silently ignores errors and people believe everything is fine …

now we finish that battle for good, we wrote a self-containing method whith instant recovery and which can handle wp upgrade or themes upgrades without the need of touching that dangy file anymore never again

“hakka security checks” is the new name

it is like outsourcing the whole private content, functions.php is just a theme owned file and you do not need to care about anymore

with a simple tap or mouse click you toggle standard actions or filters, you can add your own functions and then you enable/disable them by a click without having to care about wp or theme anymore

the hassle is over, we are giving you back the control over your wordpress site

in a couple of days specific information about SecCheck wil be posted, so keep an eye on this blog, you wouldn’t want to miss it

after reading this you can say “I saw it coming” when it hits you, and it will, as hard as it gets …

the power of that backscatter depends on you, use AI in a moderate way and you will be spared from going down, depend on it and you will fall and hit the floor, build on it and you get eliminated for good

AI is nothing more than a scam to create dependency, increase your stupidity grade, acommodate you, then you get doomed to become a stupid copy-paste operator, your creativity will be erased

it is the ultimate autoritarism implementation, appearently without violence they take you over, the violence is deep hidden in the psychological trickery of AI’s MO

the simpliest prove is Elon Musk’s stupid try to change history with falsifying facts for his groggy-shit-pedia, if it wasn’t so sad, it would make me laugh, as stupid as the temptation is it hits for now only people more stupid then the try itself

but don’t be deluded that other’s don’t do it, just more sutil, another example is the invalidation of google responses, no clear date stamp on results, fully mixed old with new, just to confuse you more and more to make you opt-in to AI

and what appears to be intelligence is just a smartass response, when they don’t have a documented answer they make things up, just out of the blue, exactly like Bill Gates did when he scammed IBM trying to sell MsDos to them, which worked out well, MsDos didn’t exist yet … imagine that happens during your heart surgery …

just observe your mobil keyboard grammer and spell checker, aren’t they failing more and more? didn’t they skip correction or have no correct suggestion for a lot of words? and why? easy, they try to get you by your weakness, make you desist and use their AI keyboards so they can better spy on you

after all that, I just can say: YOU SHOULD HAVE NOTICED ALL THAT BY YOURSELF!

so, this is your last chance, wake up! react, reject AI and keep your integrity, stay to who you are and don’t listen to machine orders! it is always YOU who control the machine, unless you give up on yourself

so what now? just think and remember what I just told you, if not you will remember when it hits you and and it will: DAMNED, I SAW IT COMING

don’t let it come so far, be smart

and that the peace will be with you
H.Mich

face it, AIs are just machines, they can’t do anything by their own, they can’t see what happens and have not organizational or strategical capacity, they might have access to a lot of historical data, but never can predict anything, they are “smart enough” to make stuff up when they don’t know a real answer and that, makes them be extremely stupid

so, let’s cut to the chase

my question:
I get the folder list form imap in disorder, how could I easy fix the order, but the bang is, abc order and so wouldn’t work, so probably I need to define an order which matter to me and order the rest as abc any, suggestion?

AI:
You want a custom sort — a defined order for “important” folders (e.g., INBOX, Sent, Drafts) and then a fallback alphabetical for everything else.
// 1️⃣ Define your priority order
$priority_order = [‘INBOX’, ‘Sent’, ‘Trash’, ‘Drafts’, ‘Junk’];
// 2️⃣ Normalize folder names
$normalized_folders = array_map(function($name){
return ucfirst(strtolower($name));
}, $mbox_list);
// 3️⃣ Split into priority and others
$priority_folders = [];
$other_folders = [];
foreach ($normalized_folders as $folder) {
if (in_array($folder, $priority_order)) {
$priority_folders[] = $folder;
} else {
$other_folders[] = $folder;
}
}
// 4️⃣ Order the priority folders according to $priority_order
$priority_folders_sorted = [];
foreach ($priority_order as $pname) {
if (in_array($pname, $priority_folders)) {
$priority_folders_sorted[] = $pname;
}
}
// 5️⃣ Sort the remaining folders alphabetically
sort($other_folders);
// 6️⃣ Merge final list
$final_folders = array_merge($priority_folders_sorted, $other_folders);

// 7️⃣ Store in DB
$mbox_upd = [
‘imap_folders’ => json_encode($final_folders)
];
$result = $wpdb->update($acc_table, $mbox_upd, $thefilter, null, [‘%s’, ‘%s’]);


me …
naaa, too much fiddling I should do that easier I do a check if matches exist in my priority and add only if not, ready
I show you how:
$mbox_list = [‘Inbox’, ‘Sent’, ‘Trash’, ‘Drafts’, ‘Junk’];
$rem_folders = imap_list($established, $srv_cnx, “%”);
foreach ($rem_folders as $folder) {
if (preg_match(‘/}(.+)$/’, $folder, $matches)) {
$mbox = ucfirst(strtolower($matches[1]));
if (!in_array($mbox, $mbox_list)){
$mbox_list[] = $mbox;
}
}

32 vs 9 … too big for any bin, let’s call another nachine to throw it in a bucket, and now dear friends, you also know why apps are growing out of bound, megabytes of garbage in all apps, megas of shit all over the place, result of stupid programming

Artificial Intelligence … pfffffffffffffffffffff

obs.: I made the exact same test with chatgpt, gemini,deepseek and copilot, there were slight differences in their answers, but at the end the same bunch of excessive garbage …

this print is from the original Skylink Theme With Colibri Editor telling that to add shortcode you need to buy the pro version

and then there are people who buy that mafia upgrade …

what the problem?

shortcode stands for a very practical and failure-free wordpress core function, so how could come some wild guy, disable it, and try to make money out of it by adding back a core function?

that’s a scam!

that really should not exist and we can not understand: HOW CAN WORDPRESS allow that ???

seems they are envolved, they get comissions for each sale … but they say:

10.5. Shortcodes: “Themes should not contain custom shortcodes… If a theme registers shortcodes, the shortcodes must be functional in the context of the theme. The shortcode’s functionality must not be crippled.”

10.6. Features & Functionality: “Themes should not hijack core functionality… Features must be functional without requiring the user to purchase a license key or upgrade to a “pro” version.”

that should be handled officially with a lawsuit against those crooks

nobody should be harmed by the plugin mafia anymore, and anybody who paid for it should get his money back

Morrison nunca teria adivinhado essa …

We don’t need no trailing slashes …
All in all it’s just a-nother quirk in the wall

o quirk neste caso sera um / … e nossa parede está crescendo, estamos prontos para receber o diploma de pedreiro mestre

wp links não são URLs absolutas, não terminam em php ou html, eles terminam com / e o core do wordpress gera o conteúdo, até aqui todo bem

quando alguém entra com uma url que não termina com slash e não tem a extensão de um arquivo, worpress adiciona silensiosamente um slash, isto em princípio também não está ruim, mas …

wordpress faz isso internamente e a URL na janela do navegador fica sem / .., esse é o funniquito

funniquito porque essa piada impossibilita o navegador fazer cache da pagina, também impede outros sistemas de cache tipo redis ou memcached gerar cache … isso porque site.com.br/conteúdo não tem conteúdo, o conteúdo está em site.com.br/conteúdo/

funniquito é apenas uma maneira de descrever “bosta” de uma forma mais elegante, mas isso ninguém entende, tem que esfregar o funnquito na cara para entender …

para quem estiver trabalhando com desenvolvimento, anote este assunto e lembre, se teu sistema de cache falha não é teu código, é pelo relaxo e curta visão dos core devs do wp … adicione sempre um sufixo “/” caso a URL não tiver e vai funcionar de maravilha, aqui é como:

 $has_ext = pathinfo($url, PATHINFO_EXTENSION);
     if (empty($has_ext) && !str_ends_with($url, ‘/’)){
           $url = $url .’/’;
     }


peace, H.Mich

OUTRAGEOUS !

anybody in contact with wordpress knows about the LLAR plugin, part of any standard wp installation, endorsed by wp org … LLAR stands for Limit Login Attempt Reloaded

look what we found:

since january ’25 we’re having an eye on LLAR because we noticed a weired pattern, after each plugin update we got a burst of blocked login attempt reports from that plugin, not much, but 10-20 for a couple of days, they came basically from two different /24 networks from the same service provider

those IP’s weren’t logged by our web server and we refined our htaccess rules, we redirected them to a catcher page and logged everything, the result was interesting, login attemps reported by LLAR were not in the log

LLAR’s reports include the login name and source IP, the login name indicates that the attempt was made by using wp-login.php, which is the only way the login name can come up

last two upgrades we got 150 to 250 fake attempts reported from this plugin, view their report below, as all the month before no trace in server log

who doesn’t is into technical, note, that wordpress cms runs on webservers with a html/php/sql environment, all incoming requests to the site are in FIRST PLACE handled by the server and then go through to the wordpress site

wordpress and none of its plugin has knowledge of what happens on the server part before getting the access request from the server ….

funny part is, together with the reports, that we, as well as you, get always an “invitation” to buy a premium upgrade in order to know more about the attempts and be safer … you probably understand already what it is about …

so are we dealing with fear-maker fake reports to trick people into paying the upgrade?

how far does it go? wp get’s comission or how is it possible that they endorse such a piece of software?

that is the right question to ask.

REMARK: if you are interesting we can provide you FOR FREE and without any condition the working htaccess rules to protect your site, together with the log-it scenario, you just need to change some lines to match your server name, just send a message and we send you the files

meanwhile, have a look at the last LLAR fake report graph

Disclaimer: We had the idea to show our good intentions and tried to report the issue to wordpress, but that idea wasn’t so good

there is no suitable contact address on wp sites
they just do what they do best, finding how to say “Core Ineligible Findings are out of scope.” and reject it

so we skip that part then

is just another stone in wp’s graveyard . . .

arguments are parameters passed to a method or function, in order to work they have defined formats, like string, number or whatever, sometimes they are optional, means you can omit them

wp dev docs explain the 7th argument is supposed to be an integer and in this case it is supposed to define the menu position, means when you add several items, with the position number you can order them in an adequate manner for their purpose, quite logical that it exist, as well as quite necessary in order not to come out like windows control panel with a wild random order . . .

then happens that the order isn’t obeyed, wp core adds the item in arbitrary order and the mess is on the table

then you find some notes about wp core function that the 7th argument is discontinued . . . hun? why that? probably they weren’t able to fix it, because it doesn’t worked anyway, they just chose to ignore it . . . hahaha

so ok, believe it, but better not, it isn’t true, the 7th argument is just ignored . . . as long as it exist and is NOT discontinued or removed, you still get an error like the 7th argument is supposed to be INT . . . haha

funny it is, but absurdly stupid, a menu without possibility to order the entries? only in a madhouse, what wp probably is . . .

how to solve it?

first, we defined our desired item order as default option

second, we have to compare the actual menu order with our desired order and reorganize it accordingly

third, the moment is the key, this has to be done after all plugins got through the wp admin ini phase, before the adm is displayed, so we hook into admin_head and run an order update

important is to run all checkes conditioned so that no arbitrary loop runs thousand times every day

of course it was an interesting journey through wp’s dark chambers and a good self-teaching lesson, but quite sad that such an extra work is necessary to compansate lazy core programmer’s leftovers . . . what is a very friendly comment

now you’re ready to dive in, or you can opt in to use our underground mainframe to be always one step in front of the crap

take care, peace!
H.Mich

why something would need a tweak?

because it isn’t good, there is no other reason, short version: read this, write it down as emergency survival instruction

it is already a shame that wordpress starts it’s installation with http:// and not by default or even forced with https://

time to wake up depps! sorry, I meant devs . . . take a strong coffe or something and get yourselves back on track, you’re still in the 90’s, or hand your cepter over, you’re too old or just not fit anymore?

finding AFTER installation the site and home url in settings is just hilarious, no explanation and no highlighting of it’s importance, anyway, it doesn’t solve the problem

this tweak
define('WP_HOME','https://ensaios.studio-one.art.br');
define('WP_SITEURL','https://ensaios.studio-one.art.br');

after instalalation doesn’t solve it, solves partially the outcome, but not the problem, some try with tweaking it in .htaccess with

#Force https
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
#

but is the same thing, just a workaround, in order to solve the problem people have to fix the database with

UPDATE wp_posts SET guid = REPLACE(guid, 'http:', 'https:');
UPDATE wp_posts SET post_content = REPLACE(post_content, 'http:', 'https:');

nobody cares until been bitten by the beast, some call us, others keep suffering, don’t know how the wp staff can sleep with their incompetence, are they mean? smiling about people getting hit by their traps?

fix it!

you guys look stupid when releasing such crap of code, you’re embarrising yourselves . . .

but don’t hang your face up there . . .

reality is on the ground, often beneath and soon you lose that contact you get lost .. watch yourself in order to stick to the truth

some cry, some think it is rude, but truth is what it is, it is the truth and it is the only ground you can construct something on, even or specially yourself . . .

Nobody tells you this. You’re encouraged to install the famous wordpress CMS to have a modern website, with very few questions asked and no good orientation. Some settings, and then, “you can do that later” . . . Well, here we go.

Sure you can.

You can go to the toilet, do your business, and decide to flush it later. Perhaps you’ll go again, think that was a good idea, and again, leave the flush for later. But when “later” comes, you see it: a pile of waste, half-dry, sticking to the walls. You now have a deep, hard, and nasty cleaning job on your hands.

That is exactly how wordpress handles its image thumbnail management.

You can do it later. But when you finally decide to change your thumbnail sizes to fit your theme’s layout, those changes only apply to future uploads. The existing mess remains untouched. They’ve just drilled a hole through the old mess to let the new stuff through, while the old, putrid pile stays put, hardening and stinking more every day.

That is your “oh, crap” moment. You realize your site is getting slow, you start fiddling around with promising plugins, but everything just gets worse.

The truth is, most people just care about making their own pile without bothering with the existing mess in the hole. So the pile grows, and so does your frustration.

Most of the thumbnail tools out there make big promises without actually solving the problem. They might remove some useless thumbnails and run a database “fix,” which means correcting the postmeta table to point to the correct files.

But the problem hides much deeper.

The standard pattern is about three thumbnails per image. So, you upload one image and now have four on your disk. That’s where it begins. Then you think you need a theme to make your site look nice (another deceit) and it silently adds a dozen more thumbnails to the pile. In one step, you can multiply your mess tenfold. If you have 500 images, you now have a pile of 4,500 new ones, plus 1,500 old ones hanging around. Imagine if you had 5,000. Your pile gets beyond 20,000.

And the best part? It’s all totally unnecessary, as the visitor’s browser makes the final decision on which image it truly takes.

So, let’s clean up and remove the pile. That’s the worst thing you can do on your own. Your site will break, with no images showing up. But don’t worry, the originals are still there, and we’re here to help

The problem still has deeper roots. Look at your postmeta database table. You might find 80k or even 150k rows of useless data there. Imagine how long it takes to find a needle in a haystack that big. Got it? That’s the final blow—most tools don’t even touch the postmeta table.

But here we are. The “wpHakka Thumbnail Revivor” does it all, with brilliant performance solving the real problem. We grab the bull by the horns—the original images—and build a new, reliable base. We don’t just fiddle with the tail, like most do.

Our process is simple:

First, we purge. We remove all the old thumbnail sizes that have been hanging around since installation.

Second, we exclude. We identify and remove any “orphans,” which are thumbnails not registered in the postmeta table and are completely useless.

Third, we regenerate. We perform a final cleanup, removing registered thumbnails with the wrong quality, then we fix the postmeta table. Finally, we regenerate all the desired sizes that you’ve selected, fixing the database one last time.

Guess what? Open your site in any browser and it pops up, just like that. All the problems are gone.

Commercial talk?

No, it isn’t. We didn’t create this plugin for sale; we created it to fix our own sites and help others. While we eventually attend to people’s needs and sell the package for a ridiculous amount, it’s just way too cheap for what it does

Think about it. Want to challenge us? You’re welcome.

We’ll refund you without any questions asked if you can show us that our promise was false, incomplete, or exaggerated. But that would be hard, because we don’t promise hot air. We promise a real solution, and that is what we deliver. [ using small letters here is just for fun ]

peace!
H.Mich

qual o bang com o nosso sub-sistema para wordpress?

uma pergunta frequente e não todo o mundo vem aqui para ler meus sarros sobre wp, outros plugins e wp devs . . . então vamos lá

o hakka commander é um substituto de todo que está relacionado com o manuseio nativo de imagens no wordpress, mas não desativa nada, funciona perfeitamente em paralelo e pode ser usado normalmente por quem quiser

hakka commander nasceu igual a fênix, das cinzas dessa imensa confusão e complicação que o manuseio nativo de imagens é, foi só para poder usar diretórios reais em disco para organizar imagens de uma forma mais racional, logo acrescentamos mais funcionalidades

um exemplo da grande flexibilidade que não só facilita, mas também simplifica e agiliza a forma de postar, basta fazer o upload de uma foto (ou selecionar uma que já está), clicar ou tapar em copiar image ID, abre automaticamente o formulário nova postagem, clicar ou tapar no + e selecionar IIBI, colar o ID, confirmar e sua foto está aí preformatada dentro de uma coluna e agora é só começar a escrever e ao terminar clicar ou tapa postar . . . pronto

outro é o manuseio básico de imagens no servidor, pode ser feito upload convencional, ou também criar os diretórios manualmente, fazer upload de lotes por ftp, scp ou qualquer outra forma, depois é só selecionar o novo diretório e importar os arquivos nele, sem qualquer rolo estão disponíveis para o que desejar dentro do wp, e muito mais

enquanto criamos este plugin muito bagaço apareceu, especialmente em termos do tratamento nativo dos thumbnails . . . melhor não entrar em detalhes, mas este tratamento é tortura do sistema, gera muito lixo, enche um só diretŕoio com milhares de arquivos inúteis e abandona no wp-content/uploads . . . não demora e seu site vira uma carroça mais lenta que um carrinho de supermercado desgovernado

dai nasceu o thumbnail revivor, é a UTI de um site wordpress com garantia de ressureição, mesmo que já morreu faz tempo . . . em poucos minutos pode elimar imagens não mais usadas ou inutilisadas, pode excluir orfãs que são arquivos tipo thumbnail não registrados, e no final rodar uma limpeza final e regeneração dos thumbnails realmente necessários

a garantia desse processo é real, funciona . . . num site com digamos 5000 imagens pode ter algo em torno de 15-30.000 thumbnails acumulados, pode ainda ter um excesso de entradas no banco de dados de além de 150.000 linhas, uma montanha de lixo que atrapalha o desempenho do seu site até a parada, com o Thumb Revivor esta quantidade de lixo pode ser apurada em aproximadamente 15-20 minutos sem atrapalhar o funcionamento do site e sem que algum arquivo original seja removido ou modificado

é só abrir o site após desse processo e no primeiro instante você percebe a diferença no tempo de carregamento da página . . .

o melhor de tudo, não é papo comercial, em primeiro lugar, não foi feito para vender, foi feito para corrigir problemas em NOSSOS sites, o sistema foi perfeicionado e durante este tempo nasceram diversas outras utilidades semelhantes com o firme prepósito de melhorar o funcionamento e acabar com problemas do dia-dia do sistema wordpress nativo

assim temos hoje: hakka Oracle, hakka PostFixer, hakka S-Cache, hakka Robo-Map, hakka Quotes, hakka Reactor, hakka Feed, hakka Gallery, hakka IIBI 3c, hakka Modal, hakka Font Changer, hakka Font Editor, hakka Alt-Txt Fixer, hakka Media Filter, hakka Lightbox Eliminator, hakka Security Add-Ons, hakka Header Meta, hakka Auto Featured Image, hakka OG:Data Fixer, hakka ImgQuality Bumper, hakka Random Img block, hakka Theme-Dark-Options Killer e mais algumas utilidades para domar o wordpress a fazer o que você quer e sair daqueles “fenômenos inexplicaveis” . . . porque não existe isso, sempre tem explicação, e não é sarcásmo, é realidade, são deficiências do sistema nativo, descuidos com a programação . . . e todo o mundo somente visa fazer o SEU produto funcionar e acaba criando desvios em cima de desvios acumulando mais lixo ainda . . .

o melhor de todo . . . nosso sub-sistema funciona 100% com qualquer instalação nativa de wordpress maior de 6.0, com editor gutenberg nativo, e com qualquer tema que cumpre os mesmo requisitos, não existe NENHUMA pendência com serviços terceiros ou plugins adicionais, também não existe esse negócio de que alguma coisa somente funciona comm módulo extra com pagamento extra . . .

e! para não esquecer, 100% responsivo, sabemos que é importantíssimo que os admins e os editores tenham acesso a partir do smartphone ou tablet com a mesma facilidade como a partir de um computador com tela grande

experimente, vai ser sua última experiência . . . e vai ser positiva.

seja bem vindo

peace!
H.Mich

nothing worse than a setback, you forgot a dot somewhere and when it comes down it hits you full, sometimes so hard that you seriously think about your capacity . . . so strong a little dot can be . . .

for immediate correction you need to sit back and stop thinking about the dot, but about what the dot just teached you, and that . . . that is the lession learn effect . . . so be proud about that it hit you, you learned something important

while doing your CSI job you probably find other wisdom in some corners, things which helped the dot hiding so long, things that made you believe the missing dot was right and much more

programmer’s life is full of setbacks, our essence, we need it, like adrenaline it rises after the correction, just before you hit the run button . . . should I, will it work, better check again?

trust yourself, go for it, you need to jump in to learn swimming, no other possibility exist . . . .