Conversation
supportI am trying out this plug-in for use on a child site under my WP Network installation. The form displays and functions as expected on the Network main site, but I created a form initially for use on the child site. The shortcode does not get the form to display there. Also documentation mentions and shows a List Name field in Form-Settings that I don’t see when configuring my form. Questions: Does the List Name field display only for the plug-in’s Pro version? Would the Pro version solve my problem with the form not displaying on a page of a network child site? The page I need help with: [ log in to see the link]
Everything should work on network child sites, but there’s one quick setup step per site. On the child site dashboard (not Network Admin): Go to Easy Subscribe → Settings Choose Allow / Skip on the opt-in box You’ll likely see a notice about missing database tables — that’s normal on multisite Click Repair Then go to Form Settings save the form again After that, the shortcode should display normally. Regarding the Last Name field: Yes — that feature is Pro-only. No need for Pro just to fix the multisite display issue. 🙂
Thanks much for the prompt response! I had already worked through the opt-in pop-up on the child site’s dashboard. I did get the ‘missing tables’ message at that point, then clicked Repair and received a success message. The form still does not display on the child site page where I placed the shortcode, although I do see Text – Before Form that I specified in Settings. Kind of puzzling. I guess I will try removing the plug-in entirely, and then reinstall it. Also, the field I asked about was L i st Name, not L a st Name. But I’ll assume that it’s part of the Pro version and not something I need to worry about right now.
No need to reinstall the plugin. Could you please send: a link to the main site page where the form works, and a link to the child site page where only the text shows? And yes — List Name is a Pro-only feature.
Sure, and thanks again for the quick response! Main site where form displays: https://blackrockimprovdesign.com/sample-page/ Child site where form does not display: https://archivy.net/news/
I think I see what’s going on. The child site is using a custom domain, and in this setup the plugin gets a bit confused with multisite + different domains. We’ll try to reproduce this exact multisite scenario on our end and work out a proper solution.
Everything should work on network child sites, but there’s one quick setup step per site. On the child site dashboard (not Network Admin): Go to Easy Subscribe → Settings Choose Allow / Skip on the opt-in box You’ll likely see a notice about missing database tables — that’s normal on multisite Click Repair Then go to Form Settings save the form again After that, the shortcode should display normally. Regarding the Last Name field: Yes — that feature is Pro-only. No need for Pro just to fix the multisite display issue. 🙂
Thanks much for the prompt response! I had already worked through the opt-in pop-up on the child site’s dashboard. I did get the ‘missing tables’ message at that point, then clicked Repair and received a success message. The form still does not display on the child site page where I placed the shortcode, although I do see Text – Before Form that I specified in Settings. Kind of puzzling. I guess I will try removing the plug-in entirely, and then reinstall it. Also, the field I asked about was L i st Name, not L a st Name. But I’ll assume that it’s part of the Pro version and not something I need to worry about right now.
No need to reinstall the plugin. Could you please send: a link to the main site page where the form works, and a link to the child site page where only the text shows? And yes — List Name is a Pro-only feature.
Sure, and thanks again for the quick response! Main site where form displays: https://blackrockimprovdesign.com/sample-page/ Child site where form does not display: https://archivy.net/news/
I think I see what’s going on. The child site is using a custom domain, and in this setup the plugin gets a bit confused with multisite + different domains. We’ll try to reproduce this exact multisite scenario on our end and work out a proper solution.