pixelonline59

I think you misunderstood.

What I’m explaining is that all my clients except one with the new version have the advanced card processing option and a block for paying by credit card.

But I have one client who doesn’t have this option. I tried contacting PayPal, but nothing has worked.

Advanced card processing is available at checkout.
I’ve indicated this via the image and also reminded you of this in each of my messages.

I see the option to pay by card, but I don’t see the ability to configure this in the plugin.
I have version 3.0.5.

https://privatebin.syde.com/?bf8cef4069d8e232#Da88XxBEANtzCPE7SerW9dqCSTXpx4ABdsvUFySqhtto

.. I don’t have this block, but I do have a card payment brick on my site…

I have this, but when I click on manage I arrive on the same page with all the payment blocks (see first image)
Every time I click on “Manage” I am redirected to this page all the time
?page=wc-settings&tab=checkout&section=ppcp-gateway&panel=payment-methods

• This reply was modified 1 year, 1 month ago by pixelonline59.
• This reply was modified 1 year, 1 month ago by pixelonline59.

Hello the update alone does not change anything.

On the other hand, if I change in woocommerce analytics type from date to date of creation it works again, however it would seem logical that this be taken into account when an order is paid.
On the other hand, if I choose “date of payment” it does not work.

Hi,

Thanks for your reply

I was finally able to solve my problem. I created a custom module that allows to remove some menu from the left bar like jetpack “remove_menu_page(‘jetpack’);” however by using this function we no longer see the menu on the left bar but we can access the page by the url except that when I access the page the dashboard is no longer displayed and generates react errors.. .

We will make it easier when I encounter the problem again, I will send you a message directly via this post with the link and you can directly view the problem and see which file is called.
If you need other information like a temporary access back I could also provide it to you.

I think it will be much easier to fix the problem.
For the moment I have a workaround so that’s fine with me but it would be cool to be able to benefit from the power of AO without having to tweak behind

Indeed the htaccess is for the cache on the browser side

In divi there is static generation of css and js files but I disabled it a long time ago.

I have just activate :
Load Dynamic Stylesheet In-line : This option dequeues the Divi style.css file and prints the contents in-line. This removes a render blocking request and improves the PageSpeed scores of individual pages. However, it also prevents the style.css file from being cached. Since the stylesheet is small, it’s recommended to keep this option enabled.
[But it’s not the problem…]

Dynamic Module Framework :Enable this to allow the Divi Framework to only load the modules that are used on the page, and process the logic for the features in use.

In autoptimize :
i have activate

Save concatenated scripts/CSS as static files?

Minify excluded CSS and JS files?

Enable fallbacks in case of 404 error?

On the other hand there is indeed a cache divi
because if I deactivate AO on the blog I can see this file
https://www.xb1204.com/wp-content/et-cache/1/et-divi-dynamic-tb-444-1.css?ver=1657034800

• This reply was modified 3 years, 10 months ago by pixelonline59.

For this particular site I don’t use any plugin type caching tools apart from
DIVI optimization, jetpack for images, autoptimize and apache specific caching guidelines

# MOD_DEFLATE COMPRESSION
SetOutputFilter DEFLATE
AddOutputFilterByType DEFLATE text/html text/css text/plain text/xml application/x-javascript application/x-httpd-php
#Pour les navigateurs incompatibles
BrowserMatch ^Mozilla/4 gzip-only-text/html
BrowserMatch ^Mozilla/4\.0[678] no-gzip
BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
BrowserMatch \bMSI[E] !no-gzip !gzip-only-text/html
#ne pas mettre en cache si ces fichiers le sont déjà
SetEnvIfNoCase Request_URI \.(?:gif|jpe?g|png)$ no-gzip
SetEnvIfNoCase Request_URI ^/wp-admin/admin\.php no-gzip -vary
#les proxies doivent donner le bon contenu
Header append Vary User-Agent env=!dont-vary

# BEGIN Expire headers
<IfModule mod_expires.c>
 ExpiresActive On
 ExpiresDefault "access plus 10 days"
 ExpiresByType image/jpg "access plus 1 month"
 ExpiresByType image/jpeg "access plus 1 month"
 ExpiresByType image/png "access plus 1 month"
 ExpiresByType image/gif "access plus 1 month"
 AddType image/x-icon .ico
 ExpiresByType image/ico "access plus 1 month"
 ExpiresByType image/icon "access plus 1 month"
 ExpiresByType image/x-icon "access plus 1 month"
 ExpiresByType text/css "access plus 1 week"
 ExpiresByType text/javascript "access plus 1 month"
 ExpiresByType text/html "access plus 7200 seconds"
 ExpiresByType application/xhtml+xml "access plus 7200 seconds"
 ExpiresByType application/javascript A2592000
 ExpiresByType application/x-javascript "access plus 2592000 seconds"
 ExpiresByType application/x-shockwave-flash "access plus 2592000 seconds"
</IfModule>
# END Expire headers

# BEGIN Cache-Control Headers
<IfModule mod_headers.c>
 <FilesMatch "\.(ico|jpe?g|png|gif|swf|css|gz)$">
 Header set Cache-Control "max-age=2592000, public"
 </FilesMatch>
 <FilesMatch "\.(js)$">
 Header set Cache-Control "max-age=2592000, private"
 </FilesMatch>
<filesMatch "\.(html|htm)$">
Header set Cache-Control "max-age=7200, public"
</filesMatch>
# Disable caching for scripts and other dynamic files
<FilesMatch "\.(pl|php|cgi|spl|scgi|fcgi)$">
Header unset Cache-Control
</FilesMatch>
</IfModule>
# END Cache-Control Headers

# KILL THEM ETAGS
Header unset ETag
FileETag none

# SECURISATION DES ACCES AUX FICHIERS
<files .htaccess>
order allow,deny
deny from all
</files>

<FilesMatch "\.(inc|tpl|h|ihtml|sql|ini|conf|class|bin|spd|themes|modules|exe|asa)$">
deny from all
</FilesMatch>

• This reply was modified 3 years, 10 months ago by pixelonline59.