xspyrox
Forum Replies Created
-
I do have the same problem on my blog for the last few days.
The thing i analysed so far is, that those fake-signups aren’t coming from the Website-Interface. the attackers seem to be targeting the php-libraries directly or using the html-form in a way, a normal user couldn’t.
Those fake-signups are assigned to no “list” on my wordpress-blog, normally when you signup, they get assigned to the list “newsletter”, even if they aren’t confirmed yet.So, maybe you could put a simple option-field in the settings of Mailpoet (i’m using latest version 2) like “deny subscriptions without explicit subscription-list” and check/validate this within the library directly, shortly before sending subscription-mail? This would solve the problem for all of us and it is really really easy to implement.
I read on other forums too that many users are having spammer-problems with Mailpoet 2 the last days.Would be glad to hear that this might be a solution you can implement next days 🙂
- This reply was modified 8 years, 1 month ago by xspyrox.
@amaravati no offense against this plugin, i was thinking about caching-plugins in general. Just named only this plugin, because we are discussing on the comment-page about this plugin 😉
But yes, that’s exactly what i thought: Cloudflare would need to get informed about small changes on wordpress in some way…
So i guess i will disable cloudflare and use only the internal wordpress-caching (namely i will use this W3TC plugin), then caching is completely controleld by the plugin, so it should be the best way for delivering cached but up-to-date pages to the user, am i right? 🙂Hey @amaravati ,
thanks for the additional information on that topic 🙂
From my understanding the WP-Plugin would be the better choice for caching because the plugin can determine better which pages have changed (for example if a comment was added) since the last caching, so the one page needs to be cached anew. Or am i wrong in that believe?Thanks in advance 🙂
Is this plugin not supported/developted anymore?
Forum: Plugins
In reply to: [Advanced Editor Tools] Failed to load plugin: table from urlmarked it as resolved
Forum: Plugins
In reply to: [Sticky Menu & Sticky Header] Submenu not working in cloned menuJust forked your codepen.io sticky (the first DO-NOT-USE version) and added a few lines:
http://codepen.io/spYro/pen/jqZjzY
This works perfekt. In my opinion it’s way easier to avoid just the jumping by creating a fake-div with 0 height/margin and to give it the geight/margin of the original div when the original div get’s fixed and so is take away from the normal pageflow.
– Less code on the page (no duplicate nodes)
– No problems with duplicated IDs (WordPress generated many unique-IDs, this could be a problem very often)
– Every other plugin should work like always, because the menu itself is never touched except for the ‘fixed’ attributeBut you have more experience with this. Can you check this and tell me if maybe there are things i didn’t think of, which could cause problems later on?
By the way thanks for codepen.io, never heard of it. Just registered for forking and it’s just great 🙂
Forum: Plugins
In reply to: [Sticky Menu & Sticky Header] Submenu not working in cloned menuHey again,
i just confirmed that it has to do with the doubled IDs.
Your code is commented and structured well, i could get myself into this. But if you are updating your plugin anyhow, your solution will most likely be the cleaner one, since you started the plugin.
I adjusted your plugin a little bit and it’s now working properly on my theme BUT only when scrolling down. The menu stays on top even after scrolling up.
I just slightly adjusted your code so that the clone-function does nothing and instead of changing the visibility, it adds the ‘fixed’ css attributes when scrolling down.
This works like charm and the submenues and JS are working like they should.
But i guess you are using the ‘original’ div to see, if the user scrolled up to that point, so that you can swap again. But since i only have one element now, there is no “mark” on the page where script can tell if it should place the element back on its original position (delete ‘fixed’).
I see my version as a proof of concept, maybe you can change your plugin this way (this method should work on CSS and JS menues).
If you didn’t understand me (I’m german, sorry for bad english), i could, if you allow, paste my changed script of yours on pastebin or something you desire.
My code is dirty though, but it shows how it’s gonna work 🙂Forum: Plugins
In reply to: [Sticky Menu & Sticky Header] Submenu not working in cloned menuHey there and thanks for the reply,
at this point i don’t have my site live.
But I tried to get into detail with my the debugging-tools in chrome:When you go to the theme demosite (http://themeisle.com/demo/?theme=Amadeus), go into debugging and copy the “Dropdown” menu-item (menu-item-56) and paste it under “contact”. After this the cloned dropdown-entry does NOT show any dropdown, though it’s the same element.
I tried changing the id to “menu-item-99” but that didn’t change a thing.
I also tried to delete the original item afterwards, but this also didn’t change a thing.If it somehow helps you i can just zip my local xampp-folder (maybe 20-50MB compressed) and upload it so you can try this for yourself.
But from what guess so far is, that the dropdown just isn’t working for cloned elements. And i think you are right about the javascript, since the fade-in effect is constantly changing addtributes, i guess by JS.
If this is a common problem with JS-menu and your plugin, maybe we can find a way to fix this together 🙂
Maybe is there any other way than cloning the menu? Or could you just manipulate the attributes from the original menu? This way it would stay the same element and would just change form and style.Looking forward to solve this and thanks sin advance
Martin