tiofelix

Dramas a parte, descobri o problema.

Realmente o CloudFlare estava bloqueando isso. Pra quem por aí achar essa thread buscando solu??o do problema, no meu caso bastou apenas pedir ao admin do server fazer isso aqui:

https://www.carlosstenzel.com/TI/como-reparar-o-problema-de-retorno-do-pagseguro-no-cloudflare/

Já esperava a clássica resposta bruta e clássica do Claudio, haha.

Meu nobre, desculpas se pareci “burro” ou se te ofendi de alguma forma, mas poxa, WordPress é uma comunidade grande, estamos aqui sempre colaborando um com o outro. Se você notar, naquele outro post que fiz, achei a solu??o sozinho e publiquei pra ajudar os outros. é normal pessoas n?o notarem um detalhe que outros notam, e … é um dos princípios de fórums de discuss?o existirem, creio eu.

Mas enfim, eu li tanto o seu tutorial que está inclusive escrito exatamente isso:

Configura??es no PagSeguro:
No PagSeguro basta aceitar receber pagamentos apenas pela API.
Você deve ativar esta op??o em “Integra??es” > “Pagamentos via API”.
Apenas com isso já é possível receber os pagamentos e fazer o retorno automático de dados.

E foi exatamente isso que eu fiz. e sim, eu testei também APENAS fazer isso. N?o funcionou, dai tentei usar as URLs dos logs que mencionei no post acima. Testes, entende? Eu só achei válido mencionar o que havia tentado. Calma, n?o é cometer um pecado arriscar outros métodos. Imagina se eu chegasse aqui falando “Ei Sanches, fiz que nem tá no tutorial, n?o funcionou, me ajuda ae.”, aí sim, na minha opini?o, parece que o cara tá com pregui?a.

E sim, mais tarde me informei sobre o phpinfo ter informa??es sobre o mod_security, fiz uma checagem e n?o havia nenhum registro de mod_security lá.

E n?o, cara, n?o testei o Cloudflare exatamente porque falei que n?o sabia ao exato um teste garantido desse procedimento e até pedi sugest?es. Quem parece ter pregui?a de ler é você mesmo. Como eu disse, relaxe.

Ahn, e testei em outro servidor também, com configura??es totalmente diferentes e cloudflare desativado. Mesmo assim, o problema permanece. E antes, este mesmo site estava em outro domínio do MESMO servidor, que tinha as mesmas configs do Cloudflare, por isso n?o acredito que tenha a ver. Só comentei porque … SIM, eu LI o seu faq.

O log de uma das compras é esse aqui ó:
https://notepad.cc/faheqa22
(Alterei informa??es pessoais do cliente e do dominio do site por genéricas só pra por neste notepad mas na hora utilizamos informa??es reais)

Opa, acho que acabei descobrindo.

Existe uma op??o nas configs do woocommerce, Settings > Products > Downloadable Products onde marcamos uma caixinha pra definir acesso ao produto após o pagamento, automaticamente.

Daí na hora de criar o PRODUTO do curso no Woocommerce, definir ele como “Downloadable”. A partir daí a próxima compra já aprovou automático.

(Só estou dando feedback pra caso alguém ache essa thread tendo o mesmo problema)

In fact, i’ve found no solution at all for this matter. Still using the plugin i mentioned on my earlier post, as it still works fine, it is just not the best solution.

But if this can help you, let me give you a couple of suggestions:

• If you only want the super admin to upload images, you can just create an account for flickr giving him the access so he can upload it in there, and then you can use one of the many Flickr plugins that allow you to post images already uploaded.
• If you are interested on using this one i’m using, you just have to do one small fix: Replace the lines 29 ~ 31 on the file lib/inc.flickr.php for these:

  var $rest_endpoint = 'https://api.flickr.com/services/rest/';
  var $upload_endpoint = 'https://up.flickr.com/services/upload/';
  var $replace_endpoint = 'https://up.flickr.com/services/replace/';

  This will make the plugin working again.

• In case you’re interested to develop your own solution, i’d recommend the imgur API, as it has OAuth, categories, etc:
  https://api.imgur.com/

  It allows you to make 1,250 uploads and 12,500 requests per day, which i believe it’s a decent ammount for most cases. Still, you can pay them to let you use more.

  There is no official php wrapper but i’ve seen some here and there while browsing github. I’ve tried to develop something but unfortunately my lazy ass haven’t managed to create anything worth sharing.

Hey there, thanks for the help, i manage to solve the problem.

They did have a backup and the host even told me what they changed, they actually just tried to run a query to change “siteurl” and “home” on the wp_options, nothing else, so no biggie, i fixed that and then ran the wp recommended script to make the changes (adding a www.)

Everything seemed to work fine but the problem i mentioned still happened.

Then i remembered the wp-config.php file holds the main website url on the DOMAIN_CURRENT_SITE constant. I changed the url adding the www. aaaaaand… Presto! the whole network came back to life.

Like i said, the host now was enforcing only “www.domain” to forward for the website path on their DNS tables so i took that guess.

Anyway, thanks for all the help, and i hope that if anyone else has the same problem, find their solution with this thread. Thank you all once again.

Hey, thanks for the help and sorry for the late reply.

Unfortunately i’m not sure if i’m allowed to post the url here, the company i work on owns it and they have very strict rules about publishing stuff everywhere. I’ll check with my boss later.

And about the serialization thing, i was aware of that and i even considered that could be the problem.

Usually whenever i want to change stuff on the database of every WP install, i use this tool.

I also wanted to ask: If i use this script on the database NOW, would that fix the serialized data and probably solve the problem? I just didn’t do it yet cause i was afraid it could cause even more problems.

About the backup, we never worried about it because it was just a development installment, and never considered the host would have a failure like that so yeah, learning it the hard way i guess.

The host might have a backup though, i’ll see if i can ask them one and change the urls by myself using the tool.

@ceviz ms Nope, i didn’t. The thread has become way too long and the forum spread it into two pages. You’re probably browsing the 2nd page. *points to the pagination on the top-right corner* Zing!

@yosua, i’ll try take a look, see if i can knack something out of it. Can’t guarantee i’ll find the solution today, though ??

@esmi Aw Hell yeah. Thank you! =D I already had a good look on the WordPress FAQ and also some articles like the one you mentioned and i had no luck.

But i never knew there was an app to scan for these little annoying and useless pieces of code.

The Sucuri site check told me exactly the only file which had a “document.write” right on the beginning which was summoning the malware somehow, and now it says that my site is safe once again, phew.

It still says that the website is blacklisted “on the Opera browser (via AVG)”. Any hint of where i should go to get my website reconsidered? Thanks in advance.

@ceviz ms Zing! I think it’s because of the behaviour of the carousel arrows.

I noticed that the pics on your carousel have this following id pattern:

ngg-image-65
ngg-image-66
ngg-image-67

and so on.

Well, when you click the carousel arrows, it CREATES a new li element, and somehow, it uses an id that it’s already being used on another picture.

I noticed this when i left the firebug window open while clicking on the arrows.

I don’t have the time right now to check on some of your js code (specially cause i’m still a js beginner, the shutter thingy i fixed was basically pure luck added with some logic.) but i suggest you trying to NOT let the arrows create new elements.

Put them straight on the HTML, and the arrows would just MOVE your view, or maybe the elements itselves, after all, what’s important it’s the carousel effect being shown, not how it was done.

Having your pics straight into the HTML open you to some new improvements:

– You can store them in a database and print using a loop.
– You can also create an User-friendly interface to add new pics.

Well, that’s it. ?? Hope i helped.

@yosua, i’ll see if i can figure it out. Can you tell me your plugin version (I think you can check it on the update plugins section on wp-admin) and also put your entire “shutter-reloaded.js” in a pastebin.com page, so i can test it with your own code?

@dom – You’re most welcome. I’m not usually able to help people on forums… (Specially when i’m the OP, now that’s even more rare) So when i do, it’s my pleasure.

Also, thanks for posting the changes on the new version of the plugin. Frankly, I wonder why haven’t the author fixed this issue yet… Maybe we should show him this thread?

@ceviz ms – Yeah… Maybe there’s a new version out there which i’m not using =P Mine is very old.

But are you having trouble finding something i mentioned?

Ahaha yes. And i’m sorry that i didn’t had time to come back here =( Things have been quite a storm here in my company.

Anyway, i’m glad i helped ya. =) Don’t forget to change the topic to “resolved” on the right sidebar on this same page.

This one works nicely. Thanks =)

YAY! Cheers! I’m glad i could help ??

And chainsaws are always pure fun. Except on web markup languages =(