platima
Forum Replies Created
-
Excellent thank you! I was looking in ‘screen options’ and ‘settings’ – where those things normally are 😅
Looks like it might be something on my host, as I found it’s the word ‘Links’ in the CSV file somehow.
Oh PS we do have URL Shortify Pro already, on two websites even 🙂
Confirmed that groups cause 403 error.
If I delete them from the CSV, but leave the header, it’s fine. With the group “1 Twitter” specified, I get a 403 error.
Hey now we just get a 403 when importing.
The sample CSV does not have a column for ‘redirect type’ – is this still supported?
We also leave the slug empty for auto-generation, else put a value in – is this still supported?
Our ‘Groups’ are usually something like “1 – Promo”, are hyphens and spaces supported?
Cheers
Thanks all good but I’m happy with my fork of the Pro version – made a pile of other changes just to make it a bit nicer to use too. Cheers
I deleted the plugin and the site is live so cannot test this for you sorry.
I’d recommend testing yourself.
FYI I literally added one command to fix this in the PHP, if that makes it easy for you;
<?php asort($groups); foreach ( $groups as $group_id => $name ) { ?>I just downloaded the zip file, extracted it, and grepped it for str_replace. I don’t know how you can deny it’s your plugin doing it, when it is literally in the damn code;
/assets/advanced-cache.php:215: $cache_key = str_replace( $replacements, '_', $current_uri );This is in the condition
has_filter( 'swcfpc_fc_modify_current_url' )So yeah, ‘modify current URL’, pretty bloody clear mate, and bricks heaps of URLs it seems.
- This reply was modified 2 years, 3 months ago by platima.
You are wrong sorry, the plugin is definitely doing this. I disabled the plugin, the problem is fixed, I re-enable the plugin, the problem comes back.
It’s also nothing to do with Cloudflare, I am not sure why you think that.
You are also incorrect about the URL parameters; a “.” is perfectly valid. This is a Shopify site, not like they’d get it wrong. Furthermore, if you read IETF RFC 3986 that confirms the legal characters.
Your arrogant response helps no one and is not appreciated.