Forum Replies Created
-
Posts
-
Hi Ismael,
indeed, this fix also works. My changes in the theme directory however will not be permanent. So, will there be a fix in the next update?
Best regards,
RobertHi,
I have a very similar problem: We have a product grid (“Produkt-Raster”) on our frontpage, and from what I can see, this is the only element with pagination. Just like @JaimBateman I see correct links on page 1, but the link to page 1 on the other pages points to the current page.For example, this is the HTML on page 3/3:
<div class="pagination-wrap pagination-slider "> <nav class="pagination"> <span class="pagination-meta">Seite 3 von 3</span> <a href="https://www.carpathia-verlag.de/?avia-element-paging=3" class="inactive">1</a> <a href="https://www.carpathia-verlag.de/?avia-element-paging=2" class="inactive previous_page">2</a> <span class="current">3</span> </nav> </div>The code snippet from @KunaWebAgency seems to work for the moment, however I think this should be fixed upstream, shouldn’t it?
Best,
RobertUnfortunately the regular German translation (de_DE) has quite a few flaws, inconsistencies and is incomplete, and I’m sorry I don’t really have the time to contribute at the moment.
However, there is one translation error that stands out, and that I keep correcting on our server since a couple of theme upgrades:
# @ avia_framework #: comments.php:179 msgid "Leave a Reply" msgstr "Hinterlasse ein Kommentar"should be
# @ avia_framework #: comments.php:179 msgid "Leave a Reply" msgstr "Hinterlasse einen Kommentar"It would be great, if you could fix that in the next release. :-)
Another idea to make enfold translations easier: I’m not exactly sure how https://translate.wordpress.org works, but it looks like you can also somehow add non-core themes and plugins. The page would allow theme users to provide translations even without installing Poedit or similar software.
Hi Günter,
are we supposed to use the github repository to provide corrected or new translations as pull request, or is this just a “read-only” copy to facilitate the access to current and historic translation files?
From my understanding using git for real version control would solve most of the problems with duplicate submissions that overwrite eachother – though not everybody is used to using git.
Regards,
RobertHi Rikard,
please allow me one follow-up question. The error was obviously related to the AVIA framework that’s bundled with Enfold and that is responsible for the advanced layout builder etc. The error however appeared on every single page of wordpress, on the frontend, and in admin, and often even twice. Shouldn’t the AVIA framework only be included, when it is needed in the first place? Why do we need to load several thousand lines of extra-code to display a settings page in admin? Or am I getting something wrong here?
Regards,
RobertThanks, Rikard, everything is fine here, now. :)
What about you, Claudio? Did the theme update fix your problem aswell?
Best,
RobertI’m still running PHP 7.4.1, but the theme upgrade to version 4.7.1 from last night fixed the problem. :)
Regards,
RobertCould this be related to the used PHP version? I started to get this error just today after updating from php 7.3.x to 7.4.1.
Regards,
RobertJust a remark: I had (and have) the exact same problem. After a little debugging I found out that Instagram issued a HTTP 429 error (»Too many requests«). Obviously the network my server is located in (hosted at Hetzner) is in some sort of a blacklist and/or issues too many requests. So it’s not Enfold to blame but Instagram/the hoster/the other users in the network segment.
Other plugins, that query Instagram directly via Javascript might still work, but this is not an option for me due to concerns about data privacy.
Regards,
RobertWe are using the following modified version of the functions to have the visitor address in the Reply-To: header instead of the From: header. (Auto-reply is not configured, so no changes there).
add_filter('avf_form_from', 'enfold_contact_form_change_from', 10, 3); function enfold_contact_form_change_from($from, $new_post, $form_params) { global $enfold_visitor_from; $enfold_visitor_from = $from; $from = "info@<domain>"; return $from; } add_filter( 'avf_form_mail_header', 'enfold_contact_form_add_replyto', 10, 3 ); function enfold_contact_form_add_replyto( $header, $p1, $p2 ) { global $enfold_visitor_from; $header .= 'Reply-To: ' . $enfold_visitor_from . "\r\n"; return $header; }Please mind that the “\r\n” has to be in double-quotes not in single-quotes!
This works for us. However, I would suggest adding a “use Reply-To: instead of From: header for visitor address” option to the contact form settings.
