iThemes Security: Pro Support
To protect our customers’ websites, we rely on iThemes Security Pro. Unfortunately, the iThemes Security Extension can only manage the functionality of the free version and not the additional options of the Pro version.
Hi MainWP team, I’m using MainWP just for a few days and it is very good helper. I’ve tried Advanced Uptime Monitor with NodePing and that was interesting. I also considered Uptime Robot but then I’ve met HetrixTools Uptime Monitor - https://hetrixtools.com/uptime-monitor/ 3 and it has been a clear choice. They offer 15 sites for free even with SMS notification and this is very important for me. So I just want to ask if you would consider implementing this service into a AUM add-on?
Hide My WP Ghost work plugin tech support response: "Seems that for your website, MainWP needs the wp-admin path unchanged. We checked with different configurations and I could sync the MainWP Child and update the plugins and security only when the wp-admin was unchanged." Can you make a setting in MainWP so that when adding a site there is a field where you can specify a different admin path? that MainWP worked if instead of wp-admin I specify a different path, for example site-name-admin. that is, the path to the plugins will not be the same /wp-admin/plugins.php and such /13-admin/plugins.php or any other path to the admin panel that I need. This is an important security feature that hides WordPress from users. do you need to make an official request from Hide My WP Ghost tech support? or you will make compatibility without it. I want MainWP to work well with Hide My WP Ghost, but now I have to disable the function that hides the admin area
I used CleanTalk on all my client sites to help stop spam. They do regular reporting each month, as well as useful quick views to check if a contact form submission was truly spam. It would be brilliant if we could pull that data into the MainWP dash and reports.
I think it is really time for MainWP, to support Gutenberg. It might have had its problems when it first came out, but it is the new standard for more than a year now and works perfectly fine now. It even has a classic editor block included for all those who still want to work with that. I tend to remove the classic editor plugin wherever I can (already at 80% of my clients). The truth is: Gutenberg is a great approach in its current state and a valid alternative to plugin based layout editors. And totally independent of what you guys personally think of it, it is there and won’t go away. So I really think it is time to respect this move from the guys at automattic and show that MWP is up to date. Just have a look at the folks at Toolset.com 2 for instance. They were not convinced in the beginning but are successfully and totally moving everything to Gutenberg now. And it works. And it is a sign of professionalism. Just my two cents. Thanks for reading. Also I don’t think that this actually is a feature wish but something that inevitably will come and therefore needs far more attention and an official statement. The chance of an upgrade like it was done with MWP 4.0 did not include Gutenberg was a huge drawback.
Hello, I would love to be able to ignore the current update for WordPress, plugins and themes. When a new version comes out, I would like to see it re-added to my list of updates. Use case: I didn’t update my sites to WordPress 5.5, but I waited for at least 5.5.1. I didn’t update to Elementor 3.0 on my sites, but I waited for the first minor updates. Thanks.
Is it possible to extend the Security Scan for each website? There are a couple of checks already in place. I would like to add one to remove the license.txt since it’s next to the readme.html, this should not be so difficult? Or is it already possible for me to add this to the database and make it work like that? Thank you. Andy
Hi, Just a though,would it be possible to make it so the left hand menu could collapse like the wordpress dashboard can. If you know of some css or php that I can add to the custom plugin you released a while back then that would be fine too. Hopefully others think this is a useful idea.
I'd like a list of all plugins across all sites under management I can see the plugin list per site by going to each site, but I want a list of all the plugins (and Ideally an expandable list of the sites using the plugin). A tree list of plugins with an expandable list of sites using the plugin would be great. Also: Listing the plugins for the sites horizontally across the page is a horrible way to show them. I can't make my screen wide enough. At least allow the page to use sliders/elevators so the screen can scroll horizontally. An expandable tree list here would be best as well
On the manage plugins page, I have two websites each with 60 plugins. I would love a configuration setting that will allow me to have the sites as columns and the plugins as rows. I would find that much easier to navigate and visualise what is installed, if I was scrolling down a list of 60+ entries rather than scrolling horizontally
I think we need to have a way to disable specific sites from being maintained by MainWP without completely disconnecting the site in case we want to reconnect it at a later stage. This is good to manage clients who are actively paying for their site to be maintained.
We need to get rid of that old redundant token system. Currently, we have “Boilerplate tokens”, “Client report tokens” and “Client Report Pro tokens”. So MWP requires us to actually enter the same data three times. And if we have the same owner for different websites even more often… What we need is the following: Introduce a “website owner” content type We can associate different websites to the same owner We have a consistent set of tokens which can be used in any extension that uses variables. Please give this a much-needed overhaul as this has been discussed already several years ago. Such little things really can make a difference.
Hi, I have multiple clients who want to see not just sessions (“website visits”) and % new sessions (“new visits”) as you’ve called them, but the actual number of site visitors (ga:Users) and of those, who are new (ga:newUsers). Is it possible to add these in as tokens, so those of us that would like to give our clients the extra data can customise a report template with them? If anyone has got these working, would you mind sharing the code please? I can’t get my head around the Analytics API well enough to custom code these right now! Thanks, Emma
Hey guys I see you have an extension for Yoast SEO, but I’m pretty sure SEOPress is really better than Yoast lol Can you please take care and add an awesome addon for SEOPress? I believe reports and suggestions (also perfomance) it’s a great way to take care.
For the Recent Post it is Ok to show them by Issue Date on the Dashboard, but for the Recent Pages I would prefer to see the Update Date instead or in addition, because they are more often updated than created new. The Pages for all my sites a pretty stable and there since month, but they get regular updates by my and also by the clients. Would be helpfull to see a list of recently updated pages using Gutenberg by the client for quality control.
The plugin manager search functionality is great, but it would be even better if admins could search whether a plugin is missing, rather than present. All it would require is a tick box such as: ‘Display sites NOT meeting the above search criteria’. Based on the results, admins can then take action and install the plugin on the sites where the plugin is missing.
Like many people, I create a child theme for each site. When viewing my themes in MainWP I see the child theme names (which are usually the site or business name) and it doesn’t really tell me much. It would be super awesome if it could somehow show the name of the parent theme.
TL;DR The default ability to easily delete a Parent Theme can completely break a site. Shouldn’t be so easy to do. I was quite shocked that MainWP would happily allow me to delete the parent of my active child theme. Working in MainWP allows for sweeping changes, and it’s my contention that any parent of the active Child Theme should not be removable. They should be locked by default and, if one really wants to remove it for some unimaginable reason, one should have to affirm multiple times.