micasuh

Hello @kloon, our experience mirrors @grangep for shipping address validation. I did not experience any need for validation using WooCommerce Shipping & Tax, but with this new plugin, every new order seems to require validation now. This is a regression and less ideal UX for us trying to purchase shipping labels.

It’s hopeful to hear that you’re working on a new feature to help customers fulfill the validation on the front-end, as it’s more important that they get it correct before it submits into WooCommerce.

Thanks for your support.

Hi @jenhooks, thanks for the reply.

I am not sure why you are seeing 11.5 on your end, it’s definitely the updated 11.5.1.

You are correct that /wp/ is the subfolder, and you update on your system fixed our issue.

Is it possible to know why this became an issue? This is a long existed domain using the subdirectory of /wp/ and it was previously using Jetpack successfully before the issue showed itself.

@bruceallen I am not having success activating Jetpack. Is anything else I can try to get this activated? Thanks for your support.

@bruceallen thanks for the reply!

I am using Jetpack 11.5.1 to attempt the Jetpack set up when I’m getting the errors.

What else should I be doing to fix this?

Thanks for the update on the minor issues to know that code is going away. I’ll let you know if this issue appears in the next updates.

As for SVN, it’s a public repo that is meant for releases only, on purpose. WordPress Docs explicitly state SVN isn’t for development.
https://developer.www.ads-software.com/plugins/wordpress-org/how-to-use-subversion/#dont-use-svn-for-development

I know developers who use git for version control for public development before submitting the latest release to SVN to release updates. Providing the ability for pull requests from community, while it might be just me who’s interested in this idea, would help your audience and customers interact even more with your plugins.

Hope that helps!

@mrclayton Your customer support is admirable and impressive. I appreciate you taking my words into consideration and so quickly. As an advocate of open source software, I’m always looking to make sure code is transparent and secure. Thank you!

Thanks again, Mr. Clayton, I will take this into account as I test with this plugin.

Thanks for the quick reply, Mr. Clayton. I appreciate your clarity on this but it leaves me with more questions.

I’m confused why account_id and client_id are not directly sent to Stripe or Plaid?

I did not know about your Connect Integration. Where you say we are giving you Platform access to the Stripe account, this is another connection I worry about the sensitive information. I understand the desire to add support requests and easy access to log files, but this means customers of your plugin are trusting you and can’t see what you’re able to do.

Will you ever provide a way to make direct connections to Stripe and Plaid without the third party connections to paymentplugins.com?

The answer is way down in ticket 5305.

I believe this post is where the chain of devs stated this is a feature and not a bug.

I don’t know how to state my case on the ticket I created because I disagree with the outcome of what they’re trying to do specifically for /%postname%/ since it’s designed to fix a problem with date based permalinks.

I also don’t understand @dd32’s comment about WordPress not supporting numeric based slugs when it seems clear that /%post_id%/ is this support as a permalink?

His solution is to use wp_unique_post_slug but I’m not versed enough in PHP to know how to do this. Maybe someone reading this could help develop a plugin based around this function? Seems like it should be possible to do what I stated in the first post, which is to use the Post ID for titleless posts, checking with the wp_unique_post_slug function to make sure it’s unique?

What am I missing?

• This reply was modified 7 years ago by micasuh.

Thank you for the feedback! I have reported this as a bug:
https://core.trac.www.ads-software.com/ticket/43593

That’s correct but that is not the issue.

Using a permalink structure of only /%postname%/, it is not possible to create a post without a title which uses a slug without -2. That’s the issue I’m trying to solve.

In other words, because I choose to use only /%postname%/, WordPress is forcing un-titled post slugs to default to the Post ID and appends -2 on every published post that does not have a title as the auto-generated slug.

My only alternative, which I’m trying to avoid, is to manually create a slug for posts that do not have titles.

• This reply was modified 7 years ago by micasuh. Reason: clarification
• This reply was modified 7 years ago by micasuh.

I did not know that %post_id was an option but that’s what I want, thank you. However, I do not want to completely convert my permalink structure from %postname%. Is there a way to target certain posts to use a different permalink structure?

Nice suggestions, thanks!

1. I previously deactivated all plugins, same result. On your advice, I deactivated all plugins again, same result.
2. I switched to Twenty Seventeen and added a saved a new post, same result. phpMyAdmin result here
3. I did not know about Health Check, that’s great! But I didn’t need to use it this time since I tried the previous two steps

For any new post, I am not adding a title. The permalink defaults to the Post ID. Thus, there would not be any old post with the same permalink. I also do not have any trash or draft posts, those are clear.

This is just part of the Revisions system. What you’re seeing is the first ‘revision’.

Is it supposed to save the post and first revision at the same time?

You can see in the image I linked to that the post has an appended -2 to the post_name column for the permalink and my assumption was because it had to create the additional Insert post.

• This reply was modified 7 years ago by micasuh.