Forum Replies Created

Viewing 15 replies - 1 through 15 (of 21 total)
  • Tem que ativar o webservice no painel deles (e a interface é bem confusa)

    No painel deles se vai em ARQUIVO -> INTEGRAÇÂO …

    Escolhe “TEX” e qualquer uma das plataformas q tem para escolher. Isso vai gerar um usuário/senha/código de usuário pro webservice. Dai para de dar o acesso negado.

    Até ai eu cheguei, mas o api dai da erro para esse tipo de serviço STD. Eu consegui ‘rodar’ o plugin usando o codigo “EXP” (express).

    Se eu achar um manual atualizado disso com mais códigos passo aqui avisar

    Não sei se resolveram ai, mas num post antigo aqui tem uma solução paleativa que deu certo aqui: desabilitar valor declarado.

    Mesmo problema, pelos logs o plugin está completamente nao-funcional.
    Ele faz o request com todas as medidas para cubagem, mas passa um peso 0.
    Vocês tiveram mudança de plataforma?

    Estou verificando ainda mas acho que no caso aqui o problema começou após uma migração.

    Thread Starter vbkun

    (@vbkun)

    Working.
    Nice solution, adding the filter to change the form itself, I haven’t thought about implementing it like that!
    Thanks 😉

    Thread Starter vbkun

    (@vbkun)

    Well as I mentioned… The admin panel only allows adding built-in field types, not additional field types from plugins.

    (but if I went to the trouble of finding the method which gets the settings from admin panel and created a filter there… I guess it was clear I knew the panel screen :P)

    Thread Starter vbkun

    (@vbkun)

    HI @mateuszgbiorczyk
    Clean code but if you notice my opening post, I wasn’t trying to include post types to search :).
    I was adding additional ACF data-types for search. (So I don’t see how using pre_get_posts can help)
    I have a bunch ACF Field types I coded myself, not to mention all the ones available in plugins repo, and didn’t found any other way to include their data type to Better Search.

    I’m trying to find a way to deal with the subject/contents of CIMY email’s before it hits wp_mail, but I have no idea how to do it without modding it.

    What you can do is look in wordpress for the filter ‘wp_mail’ ( https://codex.ww.wp.xz.cn/Plugin_API/Filter_Reference/wp_mail ). This filters runs inside wp_mail and will allow you to do any sort of modification to any outgoing email.

    Thread Starter vbkun

    (@vbkun)

    Exact same problem i’m having… still haven’t found a solution -.-

    Thread Starter vbkun

    (@vbkun)

    I did some more testing and html checking… this might be a problem in the main qtranslateX code, not this plugin acf qtranslate.

    The hidden field, which gets all lang values stored, is printed correctly. The language switcher seems to be what is messing things up.

    More over I tried disabling ACF Qtranslate plugin and well… QtranslateX still took over and fiddled with ACF wysiwyg fields. Apparently when they dropped the support for acf’s fields… something went wrong with wysiwyg and it still attempts to swap it’s values? (causing a big mess when acf qtranslate comes to play)

    Forum: Reviews
    In reply to: [qTranslate X] Working ;)
    Thread Starter vbkun

    (@vbkun)

    (ok can you help me on how to edit this rating? oo)

    —edit

    done 🙂

    Forum: Reviews
    In reply to: [qTranslate X] Working ;)
    Thread Starter vbkun

    (@vbkun)

    Nah I’ll change 😐

    I wouldn’t say due support thou… I mean in the post it was clear something was acting up and it was the language code (thanks god that post existed, its what saved me :D), but no one was near to guess the guy’s problem was the language… 🙁

    But I don’t want to be too critic here… I know how something like this get trought… specially when pt-br is the only exception, its not the most commom language and well, you guys are coding from previous works… so I understand how it can go trough 🙂

    And well, not really a ‘better documentation’ case… it was the built in setting I never dealt with :|. I mean, I didn’t set ‘pt-br’, it was there from the install :(. When i suspected of the code… the own verification of the field did not allow me to set pt-br, nothing better than verification fields :).

    Btw, thanks again for the hard work, really ^^

    Forum: Reviews
    In reply to: [qTranslate X] Working ;)
    Thread Starter vbkun

    (@vbkun)

    John just a side note… nice if you guys could add some big warning on it asap….

    While trying to solve my errors I found a bunch of people on the forums that seemed to have the exact same problem as me… but were not even near to find out the pt-br was the problem 🙁

    Forum: Reviews
    In reply to: [qTranslate X] Working ;)
    Thread Starter vbkun

    (@vbkun)

    Hey John 🙂

    Thanks for the reply but no, it wasn’t an acf problem.

    I had the exact same problems without acf. As I stated above… qtranslate X just ‘colapses’ with the 5 chars ‘pt-br’.

    It can’t understand redirects, the content filters fail (custom field or default ones), etc.

    But all is soved so far for me

    Forum: Reviews
    In reply to: [qTranslate X] Working ;)
    Thread Starter vbkun

    (@vbkun)

    I managed to get it working…

    Everything is running fine and perfect now, aparently qtranslate-X can’t handle 5 chars lang prefixes, in my case pt-br, which came re-configured in it.

    After deleting portuguese (pt) and changing pt-br to pt everything is fine, custom fields, regular fields, redirects, etc.

    Have you tried using Portuguese instead Portuguese Brazil?

    I’m having loads of problems with qtranslate-x, I managed to get some infinite loop causing error in my server where it redirected to pt-br/pt-br/pt-br/pt-br/pt-br/pt-br/pt-br….

    I also at some point managed to get the same problem as you.

    In the end just seems qtranslate-X can’t deal with 5 chars language codes… just 2 chars…

    Therefore when you try to open https://ferrao.eti.br/pt-br, pt-br is not recognized as language, but as page. So you get redirected to the pt-br page in english :).

    (if you get to solve that you may face the permanent redirect problem, which I couldn’t here either)

    ps: I believe you guys were in the wrong track as this does not relate Nginx at all, I’m actually on Apache.

Viewing 15 replies - 1 through 15 (of 21 total)