Title: oitent's Replies | WordPress.org --- # oitent [ ](https://wordpress.org/support/users/oitent/) * [Profile](https://wordpress.org/support/users/oitent/) * [Topics Started](https://wordpress.org/support/users/oitent/topics/) * [Replies Created](https://wordpress.org/support/users/oitent/replies/) * [Reviews Written](https://wordpress.org/support/users/oitent/reviews/) * [Topics Replied To](https://wordpress.org/support/users/oitent/replied-to/) * [Engagements](https://wordpress.org/support/users/oitent/engagements/) * [Favorites](https://wordpress.org/support/users/oitent/favorites/) Search replies: ## Forum Replies Created Viewing 7 replies - 1 through 7 (of 7 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WP-SCSS] PLUGIN AUTHOR PLEASE REVERT 3.0. It’s breaking sites. Check your support topics](https://wordpress.org/support/topic/plugin-author-please-revert-3-0-its-breaking-sites-check-your-support-topics/) * Thread Starter [oitent](https://wordpress.org/support/users/oitent/) * (@oitent) * [3 years, 5 months ago](https://wordpress.org/support/topic/plugin-author-please-revert-3-0-its-breaking-sites-check-your-support-topics/#post-16294631) * Hey, thanks for updating it. I’m actively looking for people to help maintain this plugin. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WP-SCSS] Update 3.0 causes critical error. Please revert!](https://wordpress.org/support/topic/update-3-0-causes-critical-error-please-revert/) * [oitent](https://wordpress.org/support/users/oitent/) * (@oitent) * [3 years, 6 months ago](https://wordpress.org/support/topic/update-3-0-causes-critical-error-please-revert/#post-16213866) * I have 38 sites with the plugin installed… This Friday was awesome. All of them broke at the same time. Most of them running paid traffic. About to try the fixes… Disabling auto-update for this plugin forever. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[TailPress – Tailwind for WordPress] Inconsistent Loading](https://wordpress.org/support/topic/inconsistent-loading-2/) * [oitent](https://wordpress.org/support/users/oitent/) * (@oitent) * [3 years, 8 months ago](https://wordpress.org/support/topic/inconsistent-loading-2/#post-16032822) * Hi guys. I’ve had the same issues and was able to replicate the problem. It loads perfectly on pages but on posts is very inconsistent. Also, it seems to have some conflicts with caching, snippets and styling plugins, but I could only confirm that enqueuing styles or files will interfere on the outcome. The order you do somethings matters. So if you clear the cache and then republish a post, Tailpress will show up, otherwise it wont. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[TailPress – Tailwind for WordPress] tailwind config](https://wordpress.org/support/topic/tailwind-config/) * [oitent](https://wordpress.org/support/users/oitent/) * (@oitent) * [3 years, 8 months ago](https://wordpress.org/support/topic/tailwind-config/#post-16032183) * Hi guys, thank you so much for this plugin. I have a question regarding theme css. I’m using Tailpress with Flatsome, but for some reason, the base css for the theme is in conflict with Tailpress. Is there a way to avoid this? I’ve seen that the preflight comes disabled by default. But for some reason the conflict still exists. * Regards, A.R. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Claudio Sanches - Correios for WooCommerce] Erro no auto completar no campo estado](https://wordpress.org/support/topic/erro-no-auto-completar-no-campo-estado/) * [oitent](https://wordpress.org/support/users/oitent/) * (@oitent) * [5 years, 2 months ago](https://wordpress.org/support/topic/erro-no-auto-completar-no-campo-estado/#post-14229459) * Estou com o mesmo problema. Isso é incompatibilidade do plugin com a nova versão do WooCommerce. * Espero que os desenvolvedores resolvam este problema ou ao menos nos dê a opção de desabilitar o autocompletar, já que o plugin não tem uma tela de configurações. * É importante ressaltar que para lojas com muito volume, a demanda de suporte ao usuário e a quantidade de pedidos com o endereço errado são um problema gravíssimo! * Por favor nos notifiquem dessa atualização! - This reply was modified 5 years, 2 months ago by [oitent](https://wordpress.org/support/users/oitent/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Claudio Sanches - PagSeguro for WooCommerce] Que feio! O e-mail ou token do PagSeguro são inválidos amiguinho!](https://wordpress.org/support/topic/que-feio-o-e-mail-ou-token-do-pagseguro-sao-invalidos-amiguinho-3/) * [oitent](https://wordpress.org/support/users/oitent/) * (@oitent) * [6 years ago](https://wordpress.org/support/topic/que-feio-o-e-mail-ou-token-do-pagseguro-sao-invalidos-amiguinho-3/#post-12855314) * Após muito pesquisar, descobri a solução do problema. Se o seu email e token estiverem corretamente configurados no PagSeguro e você não tiver personalizações de checkout configuradas, o problema está no plugin Campos de Checkout (Brazilian Market on WooCommerce), complementar aos plugins de pagamento PagSeguro e Mercado Pago do Cláudio Saches. Você não pode deixar a opção “Exibir Tipo de Pessoa” como “nenhum”. Sugiro também deixar habilitado somente “Habilitar Máscara de Campos:” e “Validar CPF”. Salve as novas configurações e pronto, tudo volta a funcionar. Faça um teste com Boleto para garantir. Visto aqui: [https://www.youtube.com/watch?v=aK0-wx-LRO8](https://www.youtube.com/watch?v=aK0-wx-LRO8) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Recent Posts Widget With Thumbnails] Gutenberg Ready?](https://wordpress.org/support/topic/gutenberg-ready-4/) * [oitent](https://wordpress.org/support/users/oitent/) * (@oitent) * [7 years, 5 months ago](https://wordpress.org/support/topic/gutenberg-ready-4/#post-11030354) * Hey! So, im new to the plugin and can attest to its really cool setup. Unfortunately Gutenberg is in fact messing it up. What i found is that when it comes beneath any block that uses lists, it gets mixed up with it. Even when using the shortcode block. I figured it out by checking with the inspector and confirming the code was within the previous block divs and lists… I guess that the shortcode block is shortcoded ‘lol’. Anyways, what I had to do was put it before the other block on that specific page. regards. Viewing 7 replies - 1 through 7 (of 7 total)