werdpres
Forum Replies Created
-
i don’t use pagebuilder – just the classic WP editor and the 2016 theme
that solution won’t really work for me – i think the purpose/advantage of having a short-code is so one can place the signup form wherever they want – i don’t understand why this isn’t working with Alert Me – i wrote a very rudimentary plugin that displays some info about the post/page and that info shows up wherever i place the short-code in the post/page
for me, i’d like the form to display at the top of the page in some instances, but at the bottom in others
Are you trying to place the subscribe box in the middle of the page, or sidebar?
in a page – if i create a page with the content…
1 [alertme-form-show] 2
the form on the published page will be placed before ‘1’
the #7 issue in the OP is no longer important to me – although i have a lot of pages, i realized that i only wanted the form to appear on a small number of them after all, so the manual insert option worked fine for me – that said, i still think it’s a feature that others may find useful
some other issues/suggestions…
A. the settings for Alert Me is a sub-menu of the WP ‘Tools’ menu – this should be moved to ‘Settings’
B. the shortcode doesn’t seem to insert the form in the right place – in my case the form is always inserted above the post/page text even when the shortcode is placed below the text (using 2016 theme)
C. if one uses the shortcode, how does one send an update notice to subscribers if all post type options are disabled in settings?
Forum: Plugins
In reply to: [Subscribe to Category] Does not work in WordPress 5.5confirmed – plugin 2.3.1 with WP 5.5 causes substantial breakage in the back-end
for example, none of the text link options (status, visibility, etc.) for the classic editor work – on /wp-admin/plugins.php checking the bulk options checkbox does nothing – there are other issues as well
i understand you had/are having a health issue, so no hurry on this
Forum: Fixing WordPress
In reply to: Link options no longer working — WordPress 5.5problem for me was Jeff Star’s 7G firewall – see here
dropping this here in case anyone else runs into this issue and finds this thread…
in my case i’m using Jeff Star’s 7G firewall (htaccess version) with the 7G Addon (perishablepress.com/stop-aggressive-scanning-uploads/) and the editor problem was caused by a bit of code in the addon – Jeff has since fixed the issue
this also solved the console error i mentioned above
Forum: Fixing WordPress
In reply to: 5.5 update broke TinyMCE (classic) editorSOLVED: in my case i’m using Jeff Star’s 7G firewall (htaccess version) with the 7G Addon (perishablepress.com/stop-aggressive-scanning-uploads/) and the editor problem was caused by a bit of code in the addon – Jeff has since fixed the issue
this also solved the console error i mentioned above
thanks Chris – i’m hoping this might be trivial to implement in that you can pretty much leave everything as-is and just keep the ‘Show alert me box.’ visible so that the plug can be disabled per-page (when auto-insert is enabled)
hi Chris
Regarding item #2, if this was dynamically generated, how would you control the content that appears on this page? What would be the benefit of doing this?
i don’t know how the content is generated, but i’m sure there’s a way to do this (i’ve seen it done in other plugins) – as for benefit, the user wouldn’t have to create a page … this is a trivial request of course, nothing super important
re #4 – yes, this too is a minor item for me
#7 is the most important to me – i have 117 pages and it’s not feasible to add a shortcode manually in order to exclude a the few pages where i don’t want the plugin to load
Forum: Fixing WordPress
In reply to: 5.5 update broke TinyMCE (classic) editorthe only errors i’m seeing in the browser console are…
GEThttps://[domain]/wp-includes/js/clipboard.min.js?ver=5.5 [HTTP/2 403 Forbidden 163ms] GEThttps://[domain]/wp-includes/js/clipboard.min.js?ver=5.5 [HTTP/2 403 Forbidden 60ms]
this is when i load a page/post for editing
vanilla Firefox
hi Andrew – Enable jQuery Migrate Helper plug didn’t help me and i’m seeing other similar reports of a broken MCE editor, so this likely has something to do with the 5.5 update – marking this as resolved
found this in WP support forums but adding the ‘Enable jQuery Migrate Helper’ plugin didn’t help me
Forum: Plugins
In reply to: [Subscribe to Category] feature: notify on page updatethanks for the reply
so the object i have in mind is to fill a gap in WP where readers can be notified when a page is updated without having to make a new post and this is not possible via RSS (absent a plugin perhaps, but not everyone uses RSS)
i think a simple label, name field, email field and a submit button would be needed that can be auto-inserted globally (all pages) at page top/bottom via an option or manually via shortcode
in the editor, a checkbox could be added which could be used to manually insert the form, or override insertion if the auto-insert option in settings is enabled
the only purpose for the name field would be so that a {name} variable could be used in the email template to personalize the mail
CSS could be external provided classes/id’s are added
something would need to be done so that a minor page update (fixing a typo) doesn’t trigger mails – perhaps this might require a second checkbox in the editor (‘notify subscribers’ or whatever)
Forum: Plugins
In reply to: [Comment Reply Email Notification] feature: double opt-ini agree that a dbbl-opt-in solution is a lot of overhead and not optimal, however while it can be abused, a lot of websites use it so apparently incorporating it is better than not
that said, maybe there’s another solution such as a simple challenge-answer solution where a user-defined question is asked (i, for one, hate google’s captcha nonsense)
i think this would be far easier to implement, however a potential problem might be the loss of the option to pre-check the subscribe checkbox (the challenge would show only after checking it) – for me this perfectly fine and it could be implemented as an option where not enabling it results in the plugin working exactly as it does now