aryanduntley

Ok. The question relates to a changed taxonomy. A post with a category, for instance /cars/sports/kia-rio.htm is changed to /cars/sedans/kia-rio.htm. WP automatically creates the redirect from the old to the new url… I was thinking this HAD to be stored in the database. The old state would have to be known in order to create a redirect. But after reviewing the code for redirect_canonical in canonical.php, it appears that:

elseif ( is_single() && strpos( $wp_rewrite->permalink_structure, '%category%' ) !== false ) {	                        $category_name = get_query_var( 'category_name' );		                        if ( $category_name ) {	                                $category = get_category_by_path( $category_name );		                                if ( ! $category || is_wp_error( $category )	                                        || ! has_term( $category->term_id, 'category', $wp_query->get_queried_object_id() )	                                ) {	                                        $redirect_url = get_permalink( $wp_query->get_queried_object_id() );	                                        $redirect_obj = get_post( $wp_query->get_queried_object_id() );	                                }	                        }	                }

it splits up the url into query parameters, checks to see if the post category exists and if so then checks whether the it’s correct. If it’s not, then it just redirects to the correct permalink. Meaning that no past state is saved in the database.

Is this correct? Or am I still missing something?

The priority parameter. Still does not provide the post meta. But definitely something I overlook too often.

I’ve tried using the mapp object like so:
L.tileLayer(…}).addTo(mapp);
L.tileLayer(…}).addTo(mapp.map);
L.tileLayer(…}).addTo(mapp.map_);
L.tileLayer(…}).addTo(mapp.Map);
L.tileLayer(…}).addTo(mapp.getMap);

t is undefined or t.addLayer is not a function are all I get. Which means I am either not grabbing the correct object or I’m not using titleLayer correctly… or both.

Not multisite. Just single install wordpress. The wp-config definitions were accessed when running tests, but when attempting to send emails live, something was wrong and I continued to get authentication errors. When I commented out the wp-config definitions, and placed the password into settings manually, plain text, the test and live emails worked.

define(‘WPMS_ON’, true);
define(‘WPMS_SMTP_PASS’, ‘THEPASSWORDGOESHERE’);

this above worked fine when running the test from your admin area. But failed authentication when attempting to send emails live via wp_mail().

SSL was not working for me (not just with your plugin. Friggin worthless godaddy. I couldn’t get SSL to work in any way, not even attempting to connect via linux command line). So, I used TLS on port 80. It’s the only thing that worked for me. Works fine with plaintext password in your setting page. But with the constants in wp-config, it is only working with your plugin when running tests.

• This reply was modified 4 years, 7 months ago by aryanduntley.

I want to connect with you. How best to do that? Without publicly posting contact details here.

Ok, I will play with that a bit and let you know if it’s resolved. Thank you.

Thank you for the response. I did not readily see the api area in stackpath. I was searching for a while for some way to generate a key. Beyond that though, with the w3total cache plugin, when clearing all settings and attempting to “perform the integration”, there is only maxcnd available and when you attempt to integrate, it redirects to maxcnd for login and obviously, stackpath credentials do not work here.

Still, I do have the API creds now for stackpath and I thank you for bringing that to my attention. I will try again on staging to see if maybe this issue can be resolved, but with the authorize and access token url’s being for stackpath, I doubt that w3t will check that path instead of maxcd since there is no stackpath option in the CDN list.