mcdeth

awesome, thank you

Also, once everthing enabled I couldn’t see express checkout button anyway, turns out it was because client id was missing (Even though normal payment worked always without it, so its very easy to miss, worth adding a notice).

Another good thing would be to verify length of client id (I thought it’s k*** number for a moment)

• This reply was modified 2 months, 2 weeks ago by mcdeth.

Thank you, that solves the problem. One more question, are coupons created from redeemed points bonded to account or anyone can use it?

Thanks for the prompt reply. Yes, indeed, it’s the Pro version on the client’s website. Unfortunately, I won’t be able to test the free version – setting up the environment would take too much time and it’s bit more cosmetical bug for me. I just wanted to clean up the debug log. This is what I got from codex:

In permalink-manager.php the plugin calls run_permalink_manager() immediately when the file loads (line 388). That instantiates Permalink_Manager_Class, which (a) registers get_options_and_globals() on plugins_loaded and (b) instantiates all helper classes, including Permalink_Manager_Pro_Functions (lines 50–109, 115–134).
When plugins_loaded fires, get_options_and_globals() runs (lines 146–162). It calls apply_filters( 'permalink_manager_alerts', array() ), so every alert callback runs before init.
One of those callbacks is Permalink_Manager_Pro_Functions::pro_alerts() (see permalink-manager-pro-functions.php (line 268)). That method calls self::get_expiration_date() (lines 166–237), which uses multiple __() translations (e.g., lines 186, 191, 196, 200, 205, 211, 216, 221).
Because those __() calls fire on plugins_loaded (i.e., before init and before localize_me() loads the text domain at init), WordPress’ just‑in‑time translation loader kicks in early and triggers the “Translation loading for the permalink-manager domain was triggered too early” notice.
To avoid the notice, either (1) defer the alert building until init (e.g., move get_options_and_globals() to init or gate the permalink_manager_alerts filter until then), or (2) ensure the text domain is loaded before those translations run (e.g., call load_plugin_textdomain( 'permalink-manager', ... ) earlier, or avoid translation functions until init).

I hope it helps and it’s not a false positive. It has helped me so far find five other sources.

db1:keys=683597,expires=4252,avg_ttl=2128419180

evicted_keys:580307
keyspace_hits:15333759
keyspace_misses:2508765

total_connections_received:17820
instantaneous_ops_per_sec:0
rejected_connections:0

used_memory:534246600
used_memory_human:509.50M
used_memory_rss:586928128
used_memory_rss_human:559.74M
used_memory_peak:641976912
used_memory_peak_human:612.24M
used_memory_peak_perc:83.22%
used_memory_overhead:36761840
used_memory_startup:876304
used_memory_dataset:497484760
used_memory_dataset_perc:93.27%
used_memory_lua:39936
used_memory_vm_eval:39936
used_memory_lua_human:39.00K
used_memory_scripts_eval:760
used_memory_vm_functions:33792
used_memory_vm_total:73728
used_memory_vm_total_human:72.00K
used_memory_functions:200
used_memory_scripts:960
used_memory_scripts_human:960B
maxmemory:536870912
maxmemory_human:512.00M
maxmemory_policy:allkeys-lru
mem_fragmentation_ratio:1.10

No, sometimes I get an ‘error establishing connection’, but only in this specific shop. The other shops using Redis on the same server work perfectly fine. I’ll be checking for possible memory leaks… In the meantime, would increasing or decreasing the RAM be beneficial?

Here are logs, I dont see such spikes in other shops

View post on imgur.com

Rescanning template is where I failed, thank you

• This reply was modified 5 months, 4 weeks ago by mcdeth.