neikoloves

Understood Aapanel is open source free control panel and here is what I have learned so far about how it stores paths > aaPanel 8.0.2 for free https://www.aapanel.com/new/download.html

I’ll try to slip in path detection, maybe this will help others, maybe not. Thanks again.

Nginx

[Binary]
Binary: /bin/nginx
Version: nginx/1.30.0
[Configuration]
Install Prefix: /www/server/nginx
aaPanel Vhost Dir: /www/server/panel/vhost/nginx
Nginx Vhost Dir: /www/server/nginx/conf/vhost
nginx.conf (aaPanel): /www/server/nginx/conf/nginx.conf
Rewrite Rules Dir: /www/server/nginx/conf/rewrite
Pathinfo Config: /www/server/nginx/conf/pathinfo.conf
Panel Rewrite Dir: /www/server/panel/vhost/rewrite
[Logs]
Site Logs Dir: /www/wwwlogs
[Compiled Modules (16)]
- http_v2_module
- stream_ssl_module
- stream_ssl_preread_module
- http_stub_status_module
- http_ssl_module
- http_image_filter_module
- http_gzip_static_module
- http_gunzip_module
- http_sub_module
- http_flv_module
- http_addition_module
- http_realip_module
- http_mp4_module
- http_auth_request_module
- http_dav_module
- http_v3_module
[Proxy Cache]
Proxy Config File: /www/server/nginx/conf/proxy.conf
Proxy Cache Path: /www/server/nginx/proxy_cache_dir
Proxy Temp Path: /www/server/nginx/proxy_temp_dir
Proxy Keys Zone: cache_one
Keys Zone Size: 20m
Proxy Cache Max Size: 5g
Proxy Cache TTL: 1d
Active Zone Name: cache_one
Connect Timeout: 60
Read Timeout: 60
Buffer Size: 32k
Buffers: 4 64k
[FastCGI Cache (WORDPRESS zone)]
FastCGI Cache Config: /www/server/panel/vhost/nginx/0.fastcgi_cache.conf
Cache Path: /www/server/fastcgi_cache
Zone Name: WORDPRESS
Zone Size: 100m
Max Size: 1g
Inactive TTL: 60m
Cache Key: $scheme$request_method$host$request_uri
Use Stale On: error timeout invalid_header http_500

@bycrik

Thank you for your direction and help, after months of effort, we now have full override control of the plugin. A single injected file now overrides many of the files and sits above the plugin’s original code.

My primary concern is update management now: we are close to forking this plugin to introduce additional new rules and related features.

I need to decide how to proceed from here, since the direction of your future changes could really intersect with or conflict with our changes.

Do you have any thoughts or an open road map of future plans?

Hello @bycrik,

Is that the only place to control this globally, as I dig into your code I find the call for get_regular_price all over and still unsure how to make this work globally in a clean and consistent manner to do the following.

Maybe there is a better way, we just want to add an extra price field and have it follow that price field used in all the views and then have discounts broken down with the correct displays. We are also using our own shortcode version to create a message for the end results output on each view, that was fairly easy to control.

We also found no other plugin that supports retails price to be compatible with your plugin at all, they just conflict with each other and no simple way yet to make them work as they both seems to be competing for control, not to mention not programmed the same way.

It will be a mess to keep them working together when things change all the time, so we are forced to do it by hand to keep it clean or deal with so many nested conflicts of bad programming styles, so many plugins are not worth even using.

Yours is, it’s fairly well throughout, clean and simple, not a bloated ad laden, tracking mess, I just need to tweak it to make it work for my needs. 🙂

Thank you and best regards.

The primary reason we continue to look at this plugin at all is its support for custom metadata fields, which is essential to our workflow.

Using the Integration with Google (Manual Method) < this is the only way to connect when you have a larger row count, but it’s not without it’s own flaws. One example of a critical issue is the inability to auto-increment table rows beyond 1,000, which makes the tool nearly unusable at any scale.

The current workaround, either writing a snippet script or manually adding rows at GS, is inefficient and not sustainable for most users.

You’ve done an amazing job with many features, including separating the standard sheets into different post types has also been extremely helpful, even critical, as most users will have this need.

Thank you for all your efforts.

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

@bruno05 We see the same issues, regardless of how we belong or not belong to an admin group.

I apologize for the super delay @linksoftware, this one slipped by, the idea is good, but it just doesn’t work for the needs yet. So for now we have moved onto creating custom filters to try and remove some of the bloated mess inside Elementor.

@linksoftware not confirmed, but I have not tested anything else, which is why I was wondering why Elementor in itself was not masked by the changes I made. Given some time, I’ll try and spin up a dev instance and see if the same issues are present on that as well. Have you tested this yourself? Thanks again.