Davis Shaver

Sounds like the issue should be fixed:

Justin here, reaching out from Zapier. You previously notified us about an issue with WordPress where the New Post trigger event was no longer working. We’ve worked with out team to investigate this issue, and we believe this has been resolved in a recent update.

Hi @stjohnscomm @stefan-coast @wafwaf, could you and anyone else experiencing this issue please do two things:

• Create a support ticket with Zapier about the issue
• Leave a message on this support forum post about the issue https://community.zapier.com/troubleshooting-99/regression-in-wordpress-action-with-new-posts-new-posts-not-triggering-zaps-37403?tid=37403&postid=145066#post145066

Zapier said they are trying to track how many users are affected by this issue, so if we can all make sure we’re acknowledged by Zapier that should help them prioritize a fix! I know if you’re like me, this issue has put a serious wrench in your workflow.

I have a Zapier support ticket open and also started a thread on the community group. It seems to me that the cause may have been a regression from an unrelated bugfix for the Zapier<>WordPress integration. https://community.zapier.com/troubleshooting-99/regression-in-wordpress-action-with-new-posts-new-posts-not-triggering-zaps-37403?postid=144938#post144938

I am also seeing this issue.

Thanks @bingobook, that is a great reference! I’m adding it to our open Github issue: https://github.com/davisshaver/wp-rainbow/issues/50

Here’s the Github issue: https://github.com/davisshaver/wp-rainbow/issues/50

By the way, something else I thought of. We would probably want to start this with supporting only functions that don’t require any input values. That way we can hook the function up to a simple button interface. In the future, maybe we could auto-generate a simple form based on ABI.

Hey @bingobook! That’s very helpful.

At this point I’m not trying to avoid shortcode development. Would a block work for you? A workaround I’ve seen from another user is installing Reusable Blocks Extended, which allows a shortcode to be mapped to a reusable block.

One other question for you – right now, we select a network (mainnet, Optimism, etc) in the RainbowKit Login settings and this network is used to perform any token validation for login/role assignment. Would it work for you if this was the same network we used for the contract interaction button?

I’d also like to explore whether I can have the function names and ABIs auto populate from Etherscan. Having the ability to enter function selector and ABI manually would be important to have as a fallback.

Please let me know if you have any other suggestions! I’m going to mark this as a resolved for now, but I have documented the suggestion on our Github repo for followup and will let you know once we ship this.

Hi @bingobook! This is such a great idea, thank you for suggesting it.

Could you describe your use case some more? Here are a couple specific questions I have.

• Would you primarily be wanting to interact with ERC-20, ERC-721, and ERC-1155 contracts? Or would you want to be interacting with custom contracts?
• Do you picture the ABI connection working similar to how the existing RainbowKit Login button block works?

@tipboxrp really interesting idea! when you say multisig login, do you mean using a Gnosis Safe or something like that?

I have added the login idea to my Github issues list, I hope to tackle it sometime in the next few months. https://github.com/davisshaver/wp-rainbow/issues/47

Also here’s the issue I made for the caching problem. https://github.com/davisshaver/wp-rainbow/issues/48

I’m going to mark this issue as resolved for now but feel free to open another one if you see anything else to discuss. Thanks again for the feedback!

Hi @tipboxrp! Thanks so much for these notes. I apologize that it took me a few days to get back to you.

I will look into compatibility with caching plugins. I have an idea of how I can provide a compatibility option for caching plugins. Because the plugin relies on register_block_type() for enqueuing the required CSS & JS assets, I think there could be issues with the shortcode workaround that you’ve found – essentially the block code might get evaluated too late for the assets to be enqueued. So I can look into adding a compatibility mode option for caching plugins where the CSS & JS gets added to every page.

Would you mind checking one thing for me @tipboxrp – Do you see issues with caching plugins on the main wp-login.php login page? If my theory is correct, you should not see issues with caching on this page, only with the login block.

Thanks also for your tip about the custom login page. I originally built the wp-login.php integration with the goal of having web3 login and password login both on the same page. Do you think it’d be useful to have an option to disable email and password login if you’re using this plugin? I was hesitant to add this originally because I was worried about site administrators locking themselves out. Maybe if we add the option to disable email and password login, we could also generate a secret login URL. Something like yoursite.com/wp-login.php?wp_rainbow_secret_login_token=L4JRGJ6F38 where L4JRGJ6F38 is a randomly generated token stored in the database. Then the site admin could save this URL so they can access the site using email and password if needed.

Thanks again for using the plugin and sharing your thoughts/tips!

Hi @tipboxrp – I’m not opposed to adding a shortcode, but it would require additional development, and I think the block should be able to work for your purposes.

Would you be able to describe your use case for the header trigger login popup? As far as I know, Elementor is compatible with the block editor (Gutenberg), so you should be able to use the RainbowKit Login block already. If you would prefer following up via email, that’s fine with me – my email address is [email protected]. Maybe you can set me up with an author account so I can take a look at your setup and advise on how to use the block on your site.

Hi @tipboxrp! Glad to help answer these questions. I will add them to the readme but I wanted to answer first and make sure I answered all your questions.

Infura API keys were previously called project IDs, so I will update the label in settings to make it more clear that we need an Infura API key here. Without an Infura API key, token-gating and ENS integrations will not work properly.

There is not a shortcode, but there is a block for login. With the plugin installed, you will have access to a RainbowKit Login block which can be customized similar to the button block.

Please let me know if this answers your questions and what other questions or ideas/feedback you have. It would be great to hear your thoughts!

Hi @adamdunnage – thanks very much for the reply! The JS error is not breaking workflow right now so it’s not urgent on our side. I hope the ticket primarily helps with other users who may run into this issue while a new version is in the works. I popped into GitHub and saw there’s some ongoing chatter related to this. If the new version happens to not address my specific setup then I will proceed to isolate/identify the specific conflict (although I’m 90% sure it’s with Memberpress also loading the library).

Thanks @adamdunnage, just sent over the info via the Google Form!

Hi there, I’m a Newspack user also experiencing this issue. I’m not using any of the plugins mentioned previously. However I am using Memberpress which appears to load libraries from Gstatic domain. I will cross-file this issue with Memberpress as well.

`Cannot read properties of undefined (reading 'Pe')

    in GoogleChart
    in ContextProvider
    in Chart
    in div
    in GoogleChartErrorHandler
    in GoogleChart
    in div
    in WPDashboardUniqueVisitorsChartWidget
    in div
    in WPDashboardWidgets
    in div
    in WPDashboardApp
    in RestoreSnapshots
    in ErrorHandler
    in ThemeProvider
    in StrictMode
    in Root`