Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter maikbrauer

    (@maikbrauer)

    Hi @yordansoares,

    sorry for my late reply!
    I checked the Disable for setting which is empty in my case. So this seems to be OK.

    My guess is that we never reach the Status flag “Processing Order” as since the order it went to the state “Reduce from Stock” to “Waiting for Payment (from Stripe)” and then from there to “Order Completed” So I am not sure if that Status you mentioned will happen in some circumstances of an order process. Maybe is jumps over this status and goes immediate into on of the other status flags.

    Don’t we need to put the Check/Flag to the status “Order Completed”?
    Not sure which is the right status to choose and also I am not sure which status levels sometimes will be skipped depending on whatever trigger. So it might be that the status, which I have chosen to send the Invoice will never happen or only in rare cases. See my point?

    What do you think? Do you need more Debug Infos? What else can be done here?
    Thanks a lot.

    Thread Starter maikbrauer

    (@maikbrauer)

    Hi @dpeyou

    I did but they told me that we do not use the paid version. And we also have no License. So it must be the free version. Therefore they guided me here to post that question. Now you are sending me back. That’s strange.

    Cheers
    Maik

    Thread Starter maikbrauer

    (@maikbrauer)

    Hi @hyenokian,

    many Thanks for your quick response.

    I have tested the plugin with the latest release as mentioned by you.
    I can confirm that it works now and all is good.
    Many Thanks for the fast fix on this.

    Kind Regards
    Maik

    Thread Starter maikbrauer

    (@maikbrauer)

    Hi @robert681,

    many thanks for your answer on this and adding that to your feature list to be added.
    Great to hear!

    No I have no further question. Looking forward for the implementation. Are there any
    version Tags with which you want to have it implemented?

    Thanks a lot.

    Thread Starter maikbrauer

    (@maikbrauer)

    Hi @robert681 thanks for your quick reply.

    I am using the WooCommerce one: WooCommerce Subscriptions
    Version 3.1.3

    Let me know if you need something else.
    Thanks.

    Cheers
    Maik

    Thread Starter maikbrauer

    (@maikbrauer)

    Hi, thanks for the ping and also for pointing me to the correct people/group.

    No not really solved yet. So I would not call this thread as solved.
    I am now talking to the #developer channel in Slack and got already some snippets which are not working as expected. I am still trying to get this somehow done with the help of the community.

    But let’s close this thread then for now and if there is something else, I ‘ll come back here. Thanks for now and take care.

    Cheers

    Thread Starter maikbrauer

    (@maikbrauer)

    Can you tell us a bit more about this? Are you seeing failed webhook events on your server or in Stripe, or is there something else telling you the webhooks are failing?

    I am talking about the Asynchronous WebHooks from STRIPE after approx 5 working days, when the Bank reported back the sucessfull execution of SEPA. Then Stripe needs to inform the WooCommerce System via API-Endpoint (https://mydomain.com/?wc-api=wc_stripe). And exactly this call seems not to work properly.

    I can’t really see any WebHook failing on Stripe. It seems that also the logs are over the 15 days, which are not part of the logs anymore on stripe (Told them already to get that improved at least to 30 days retention)

    Also on WooCommerce, is there any option to get mire insight/data/logs for that kind of events. I could not really find any reasonable log for this.

    Also interesting to know, which are the neccessary events to be configured on Stripe for the Webhook to report the right results for SEPA Operations.

    If anything else is needed, please let me know.
    Thanks.

    Thread Starter maikbrauer

    (@maikbrauer)

    Hi @anlino

    Thanks for you quick reply. If this is not allowed as part of rules which needs to be respected, then this is fine. I do not have deep insights in the laws of WordPress, therefore I can’t judge on that point.

    Independent from that, if this “would be” allowed, I am a bit disappointed that you even then would not implement it as you see it for yourself as a niche feature. For me and possibly others it would be a nice add-on to give customers of “your theme” this possibility to exclude from start page.
    Also there is a reason why people asking for Plugin development in order to do exactly that, what the theme is not providing, as in this case I am describing.

    Customers voice is important Anders ??

    Anyhow, I tested your recommendation with the Plugin, which is exactly working as I would like to have it. So my problem is finally solved then, until the next one will pop-up. I’m pretty sure that I will get back to you with something else ??

    Till then, many thanks again for your quick answers and the hint to solve my issue.
    I also highly appreciate your support.

    Cheers
    Maik

    Thread Starter maikbrauer

    (@maikbrauer)

    Hi @anlino,

    why can’t you just put an option box in your theme customize are where you can define the categories which hitchcock theme should display at all. I just want to avoid that the theme picks it up at any possibility.

    I want to use specials posts with special categories for a plugin. For the Plugin the filtering works quite well, and I just can specify the Posts I want to have shown in that plugin area. But Hitchcock will immediately pick this up also and put it on the start page and on the other child pages also.

    Why not just putting a box inside the Wp-Admin area under your theme customization where we can define category IDs?

    Cheers
    Maik

    Thread Starter maikbrauer

    (@maikbrauer)

    Hi @anlino,

    many thanks for your support here. I the meantime I have used a trick with the style-sheet:
    `.social-menu a[href*=”xing”]::before { content: ‘\f168’; font-family: ‘Font Awesome 5 Brands’; }

    But as I understood now it should go the normal way without having my own patch.
    Thanks again.

Viewing 10 replies - 1 through 10 (of 10 total)