Alexandre Froger

Forum Replies Created

Viewing 14 replies - 361 through 374 (of 374 total)
  • Thread Starter Alexandre Froger

    (@frogerme)

    Hi @mbrsolution,

    Thank you for the fast reply.
    I did check the documentation, in depth. I did not ask about the license key. I asked about the “Secret Key for License Verification Requests”

    I indeed DO need more information: why is the “Secret Key for License Verification Requests” needed at all, from a security point of view (please see the edited OP)? The documentation does not give that information.

    Note: I DO know how to use the plugin.

    Best regards

    Plugin Author Alexandre Froger

    (@frogerme)

    Hi @alexlii !
    Actually that’s the precise reason why I developed this plugin: none of the existing code base I could find was following both WeChat AND WordPress standards, and quality was poor.
    Your feedback is really appreciated. I am currently working on and maintaining several plugin projects here on www.ads-software.com, and all is done during my free time. I will definitely test on MS because I try to address every reasonable requests whenever I see there is a demand from the community, but please bear in mind I do not have a strict timeline for that ;).

    Plugin Author Alexandre Froger

    (@frogerme)

    I am marking the issue as resolved since it is more some questions about how the plugin works than a support request – please feel free to continue the thread, I’ll reply here in a timely manner.

    Thread Starter Alexandre Froger

    (@frogerme)

    @clorith Nice – I do not wish to answer in more details (basically, doing the UX work for the dev and QA) and my review is getting censored? Way to go…

    @felix2018 you may want to change your rating to 1 star…

    Plugin Author Alexandre Froger

    (@frogerme)

    Hello @alexlii,

    First of all, thank you for your interest in WP Weixin!

    1.#

    There has been no test done regarding multisite support so far, it maybe works out of the box or not at all.
    I will investigate and report back here.
    What is sure though is the same issue as with WPML applies: if the multiple sites are on different domain, or subdomains, you will run into troubles: since WP Weixin is designed to be connected to a single Official Account, and each Official Account accepts only one value for the “Webpage authorization domain name” in “Account info” > “Function setting”, calls to the WeChat API for authentication and others (actually, limited to 3 for JS API calls) will not work with multiple domains or subdomains.
    One way to allow WeChat authentication with multiple (sub)domains would be to have one multisite instance dedicated to it (auth.yourdomain.com), with all the other instances calling it and do a multisite network-wide authentication. It may require some extra code.

    2.#

    WP Weixin is all about mobile authentication: as a matter of fact, it does not provide any authentication layer in the browser yet.

    The way it works when “Enable WeChat mobile authentication” is checked:
    – a user visits the site with WeChat
    – the user gets automatically registered and authenticated with their WeChat Union ID (and gets authenticated at each visit if logged out)
    – the user may set an email and password (but cannot change their username, remains the Union ID)
    – the user may now authenticate in the browser with their email and password

    Because WP Weixin is primarily an integration library, some extension plugins may need to be created on your end. Its goal is to provide the bare minimum features to integrate with the various APIs (JS_SDK and server calls).

    However, it does not support WeChat payment out of the box. Two plugins exist for that (WooCommerce WeChat payment gateway or direct via QR Code), but there is nothing preventing you from extending WP Weixin for your own purposes using the provided actions, filters and JS events, all documented here.

    —

    Please also note that the plugin and its associated suite supporting WeChat Pay (Woo WeChatPay payment gateway for WooCommerce and WP Weixin Pay extension) are to be used with a WeChat mainland Official Account.

    • This reply was modified 6 years, 7 months ago by Alexandre Froger. Reason: formatting
    • This reply was modified 6 years, 7 months ago by Alexandre Froger. Reason: typo
    • This reply was modified 6 years, 7 months ago by Alexandre Froger. Reason: precisions
    Thread Starter Alexandre Froger

    (@frogerme)

    Hi @mra13 – thank you for the answer.

    I understand most people may want that, although it looks more like an assumption, especially given SLM is for developers – meaning: a lot of edge cases which would require flexibility rather than a boxed-in solution, even if it means the dev needs to type – oh no! – an extra value in a field.
    If one would really want to cater for that specific case, however, the best practice would simply be to pre-populate the field with today’s date and then sync the interface with javascript to adjust it accordingly when one edits the creation date.
    That would be a way to handle the use case properly, not to arbitrarily force it on save.

    Yet, even if this was too much workload, there is still a one-line solution that could bypass this forced state: a filter before save. But there is not even a hook that allows to change the values before inserting data in the DB, meaning that any manually edited license, even if they were populated with an empty expiry date through the API, would end up with an expiry date impossible to change back to empty unless there is another API call.

    I am sorry, but no matters how we look at it, it seems the problem remains :(.

    Plugin Author Alexandre Froger

    (@frogerme)

    Hi @motivmedia

    Good news, and thank you for the feedback – that’s how the plugin will improve!

    As mentioned above, I’m working on getting out v1.2 by the end of the week (very fast version change, skipping all the minor versions for this update) and I’ll make sure to test it with BBQ.

    So far with the dev version I’ve put together, using the endpoint optimizer does the trick, but because it’s a known issue that’s been experienced by at least one person (you in this case), I’ll make sure to include more tests.

    In case you have more issues, please do not hesitate to open separate threads – I’ll reply here, no problem, it’s just it would be easier for others:

    • to see that issues are addressed by seeing the number of issues solved
    • to search for a particular issue

    Cheers!

    Plugin Author Alexandre Froger

    (@frogerme)

    Hi @motivmedia!

    So I made an error somewhere yesterday in my mu-plugin when testing the auto-updates, and I thought it would be better to use tried-and-true code out there to avoid errors of inattention.

    On a fresh install of WordPress:

    • I installed dummy-plugin (provided in the integration examples of WPPUS) and set it up so that updates are linked to my WPPUS
    • I installed Easy Updates Manager
    • I set dummy-plugin’s version to 0.99
    • I made sure dummy-plugin 1.0 is in my release repository linked to WPPUS
    • I selectively enabled auto updates for dummy-plugin in Easy Updates Manager
    • I manually triggered “Force Automatic Updates” in Easy Updates Manager (emulating the wp-cron event)
    • I saw dummy-plugin auto-updated => SUCCESS
    • I updated the code of my install of dummy-plugin and its package settings on WPPUS to require a license
    • I input the right license in my dummy-plugin install
    • I set dummy-plugin’s version to 0.99 again
    • I manually triggered “Force Automatic Updates” in Easy Updates Manager (emulating the wp-cron event)
    • I saw dummy-plugin auto-updated => SUCCESS

    I also performed the same steps above (minus the WPPUS linking) with Hello Dolly plugin as a benchmark test, and got the same behavior => SUCCESS

    So, it seems we’re all good with auto-updates, and it’s consistent with what I can see on Yahnis Elsts’ Github.

    Plugin Author Alexandre Froger

    (@frogerme)

    I’m gonna look into adding the compatibility with auto_update_plugin and auto_update_theme for v1.2 – so far, it doesn’t seem to work and it would indeed be a nifty feature! Keep an eye out on the changelog of v1.2 when it’s out! (end of this week or next week)

    Plugin Author Alexandre Froger

    (@frogerme)

    Hi @motivmedia !

    The forum was empty because the plugin is new haha! Its target audience is pretty narrow, so there’s no surprise number of comments, reviews and active installs are low at this stage.

    I had a quick look to the alternative solution, and it looks like one would have to do way more coding than with the direction I’m taking with WPPUS.

    To answer your questions:

    • Jeremy Clark’s solution is very much its own solution (not working in combination with WPPUS), and it’s similar but not as advanced as Yahnis Elsts’ – my plugin is based on the latter’s libraries, a combination of Plugin Update Checker and WP Update Server. While these solutions work fine as long as you upload your packages on the update server and build their metadata (added workload), the added value of WPPUS is to automate as many things as possible, to let you focus only on maintaining your code base on your Git repositories. Sync with the update server and the repos is fully automatic in WPPUS, and most interactions are done with a GUI when they are rarely needed.
    • I am not sure to understand – the clients using your plugins and themes will see “there is an update for the plugin/theme” automatically, yes, but it won’t be downloaded automatically like WordPress security updates. They will still have to use the Update button in WordPress admin. But here is the thing: as long as the client plugin or theme has an equivalent in the linked repos, then updates will happen: WPPUS acts as a proxy for your repos. In short: the client asks for updates > WPPUS checks repo for new version > repo gives latest package to WPPUS if needed > WPPUS tells the client there is an update > the administrator triggers the update in admin > WPPUS serves the latest package to client > the client is updated.
    • Full support for plugin icon, plugin banner, plugin changes and theme information is planned for v1.3.

      • Hope this helps!

    Plugin Author Alexandre Froger

    (@frogerme)

    Hello @motivmedia

    First of all, I am so sorry and would like to apologize – I did not see the issue, and it’s been a month. I usually make sure to reply to all requests and do my best to troubleshoot and provide solutions, but lately I have done so when contacted via email and Github – I overlooked this channel.

    You are right – the plugin was checking Software License Manager integration no matters it was used or not. It has now been fixed, albeit maybe too late for you.

    I hope you will still be able to make use of this plugin, and do not hesitate to reach out if there are any other questions.

    Best,
    Alex

    Thread Starter Alexandre Froger

    (@frogerme)

    @clorith constructive criticism has been given elsewhere – the CTA on the plugin page is “Add my review”, and the title of the form is “Create a new review”. The guidelines state “Please provide as much detail as you can to justify your rating and to help others”, which I did: Gutenberg is, in my experience (and not only mine judging by other reviews), a take at building some sort of visual composer, and not a good one. Nowhere is it stated reviews are to “provide constructive criticism” – and when I see how constructive criticism is addressed elsewhere, it’s actually a good thing the guidelines are not requiring it.

    I am not sure what there is to redact, since the ability to add poor reviews (even if it’s only to say “I agree with the other users who gave 1 star, for the same reason”, and that’s the gist of my previous comment, elaborating on my intentions and justifying my rating) is covered by the guidelines just like for good reviews (for which I’m sure redaction when not constructive is not even considered), and I gave directions as to where the answers to the question I was asked can be found.

    Regardless, this is where I stand, and will stop replying to this thread, no matters how redacted it becomes.

    Thread Starter Alexandre Froger

    (@frogerme)

    @ziogio98 seriously, potato potato..
    @clorith that’s nice of you guys always ending with questions, but given the HUGE NUMBER of complaints either here or on github, I’m wondering if it’s because you care, or just because you want people to look bad for not replying to a pointless question.
    By the way – the answer to your question can be found in these topics you guys already gave bogus answers to. I’m just here to add a +1 to the number of 1 stars.

Viewing 14 replies - 361 through 374 (of 374 total)