makobaby01

https://makobaby.com.br/

I don’t know what the problem was, nor the compatibility, but I do know that when I updated some pending plugins (I wait a while, because the plugins I use depend on another one)
And also the update of yoast seo, and it returned to work correctly!

Thank you very much for the great support that you support!

this is very strange, I installed the test site, possibly I didn’t do it correctly, but it had all the plugins and the theme (but on the official site I use custom html codes, but not that it would affect) and the plugin worked without problems, with the same active plugins, what could be happening?

@devnihil I did a test on an old website that I have, put all the plugins in, activated them all and the plugin was not working, deactivated all that was not so important, left only the ones that are crucial to my website, and the plugin worked normally , I was activating one by one and continued working, until I activated them all and it worked, I didn’t understand much, but I suspect the theme.

I’m making a backup of my active site, and I will upload it to the test site and see if the problem occurs with the theme, I will return to you for more information or at best the origin of the incompatibility, ok?

It happens when I want to edit a post / page, it just doesn’t show up anymore, so I can’t edit the title or the meta description.

I suspect google, but I will report, I also feel that the meta description is not being changed from google, but this can take time

On question 2: I wanted to take only <h1> to be more precise, in my case it is a category, I wanted to take only the name of the category

@ashucg interesting your comment, however, if you assist me in doing the following, oblige to use <picture> in all , thus ensuring that it will serve .jpg for browsers not allowed, and serve webp for browsers that support, in theory this would not affect with cloudflare, since it is a change in code, but how would I do it in code?
Like using imagemagik (I can’t remember the name) which is a conversion via php to webp, would that also change for the case of cloudflare?

Isso seria ótimo, pois a mensagem Data de expira??o menor que atual n?o faz muito sentido, na primeira vez que eu atualizei eu pensei que seria um erro, ai fiquei usando a vers?o antiga.
Mas isso seria de grande ajuda!
Obrigado.

Caso queira como sugest?o, no meu tema n?o tive problemas, mas custa nada testar!

 <!--CARD EXPIRY-->
			<p class="form-row form-row-first">

				<label for="card-expiry">
					<?php _e( 'Expiry (MM/YYYY)', Core::TEXTDOMAIN ); ?>
					<span class="required">*</span>
				</label>
			<!-- ESSA é A MODIFICA??O QUE FIZ NESTE LOCAL -->
<p style="font-size: 13px;float: left;clear: both;">Ex: 11/2021(MM/AAAA)</p><br>

Isto no editor de plugins > wirecard > templates > payment_methods > transparent_credit_card(no meu caso, checkout transparente)

Mas claro isso é no meu caso, talvez você até já fez, mas se n?o, pelo menos ta ai!
Espero que te ajude até eles aprimorarem isto!

kkkkkkkk
Isso é verdade, por que digitar 2021 invés de 21, na minha opni?o é fora de comum, porém n?o é algo t?o diferente, mas com certeza alguém poderá vir falando que a data de expira??o ta menor, por isso coloquei em cima do input EX: 11/2021, por que sen?o, terá problemas futuros

Se aceitasse os 2, seria ótimo!