cfb51
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Upgrading PHP from 7.4 to 8.2 on 15 year old websiteI just upgraded a long abandoned and heavily customized install from 7.1.3 to 8 3 and from wp5.x to current. I did two sites, in fact. The first one worked with zero issues. The second one and the one really heavily modified, fought me.
the truth is the “fixes” arent hard, they’re just time consuming. If your apache config files are set up right allowing something at all to be displayed, its a matter of looking at the source code and seeing how far it made it until it broke. It helps to know which template is serving what content. Then, find the template and line where the code broke, and Google up the changes you need to make.
I think i had to change maybe three or four lines of code in mine. I dont recall the precise operators, but it was a simple process.
dont be intimidated- just do it. Then, start activating updated plug-ins and do the same thing.
Forum: Fixing WordPress
In reply to: Still problem with iFramethere are two items in CSP, held in headers mod directives and in htaccess or httpd files… iframe and iframe ancestors.. one allows “them” to frame your site, and the other which sites you can frame.
Setting both to ‘self’ clears you hot to frame different parts of your page in, well, different parts of your page so long as its in the same home directory.. After that, be careful who you allow in and who you allow to frame your content. You can take this info and Google up a good set of rules… then, its a matter of seeing what’s broken via inspect/console errors in chrome, seeing what you need to allow by url, and deciding if you want to let them in/out, or not. This same holds true for other scripts such as fonts from cdns, js/jquery from other places, etc… all controlled within the CSP with different directives to specific use…
I dont rec you abandon your CSP especially if you’ve already been targeted before… just set it correctly… it takes minutes and will save days weeks and months of potential frustration.
- This reply was modified 10 months, 1 week ago by cfb51.
apologies for the late response…
yes. that is precisely what i’m cooking over here playing with your code. 🙂
I spoke too soon… it will need a permalink rewrite that either removes the slashes (directory breaks) and replaces them with dashes, OR, an allowance within the application to make custom permalinks and use dashes instead of slashes. Either way, it can be done with relative ease and will make your product even better.
so far- i’m digging your product- simple, clean, functional.. one of my affiliates made $35 in two hours from six sales… he’s more excited than i am!
well… i’m back… and with news you may appreciate.
yes, in fact, you DO have this feature… it’s right there in the open, too… no code, no fuss, this is how it’s done:
create or modify the product in woocommerce… change the permalink to have the affiliates ID at the end… whallah.
Forum: Plugins
In reply to: [Affiliate Program Suite — SliceWP Affiliates] Restricted CategoryI have it sorted, now, but thank you!