Lee Hodson (VR51)

Yeah, it’s a bit temperamental at the moment but I’m sure Main WP’s excellent dev team will iron out the kinks soon.

Good luck with the second part of the issue!

I see what you mean now. I thought they showed as installed in the Extensions Manager but that you were unable to access their settings.

Could be a quirk in the extensions installer that prevents extensions showing up if the pre v.4 ones are not deleted through WP Admin > Plugins. Maybe something in the deactivation uninstallation script needs to trigger so that Main WP 4 is certain the pre 3 ones have been deleted. I’m clutching at straws here, though.

Sometimes helps to use Optimize WP to check the database and delete transients.

I know you’ve cleared your browser cache. Maybe there’s a server cache or CDN cache that needs to be cleared too.

I would delete the extension files then use the Extensions Manager to install them again and send a ticket to Main WP through their website if re-installation doesn’t work.

There is a Screen Options cog at the top right of the Overview page. You can use this to enable or disable widgets. Some of those extensions might need their widget to be made visible.

Now this bit is less obvious. When you view the Extensions in the new Extensions Manager page you can click the green title of each extension to navigate to the settings/admin page. You do have to activate each extension through the Extensions manager page (there is a green button under the Test Login widget).

Do the other left-hand menu items expand and contract when you click on them? All of mine do and that’s how I access the admin page for each extension. You’ll know to check this but because others looking for answers might need a prompt I’ll say it anyway: if the menus are not expanding then a plugin script or ad blocker could be interfering with the UI.

For reference I use Opera on Linux, which is pretty similar to Chrome (same core). I’ve not tested Main WP 4 in Firefox, Vivaldi, Brave or other browsers.

I’m hopeful some of the convenience of the older layout is returned in a later release. You could be right in that Main WP are waiting for wider feedback on the present UI before they re-introduce features. You are right, they do a great job with Main WP.

• This reply was modified 5 years, 3 months ago by Lee Hodson (VR51).

This info might be of help to you.

To View Sites

In the Overview page look at the Connection Status widget. There is an inverted triangle near the top right hand side of this widget. It is just next to where it reads ‘Hide Details’. Click there and you can elect to See All Sites. This will list all sites in the Overview page and you can click to view the site admin. The problem is that each time the Overview page is reloaded you need to reset the widget to elect See All Sites.

I also have the issue that no sites show under the Sites menu but then I feel they are better viewed in the Overview page.

Extension Settings

You can view the each extensions settings page by clicking the triangle next to Extensions in the left-hand Main WP menu.

You must delete the pre version 3 extensions then install version 4 extensions by visiting the main Extensions page (accessed through the left-hand menu).

Other

A few months ago when version 4 was in alpha status I sent a support request to Main WP to express that the new UI looks nice but is functionally cumbersome because it requires users click more buttons and visit more admin pages when all most of us want to do is access site dashboards and update software from the overview page. My feedback was ignored. Hopefully enough Main WP users offer the same feedback and thereby prompt the devs to rethink the Overview page and its design requirements.

@drewstrojny Drew, I’m sympathetic to development costs. Experience tells me that most WordPress admins and developers prefer free to paid and that not many people like to donate toward development costs. I feel that pain. I really do.

However, I am also aware that developers will pay to upgrade to the pro version of a plugin once developers trust the product, trust the brand and have had time to discover the usefulness of a plugin. There is a caveat: the usefulness of a plugin needs to warrant the cost of the upgrade.

A few months ago I was ready to purchase HappyForms. I was a happy HappyForms user. I promoted HappyForms to other developers and influencers. I originally became aware of HappyForms through other developers, specifically a theme developer who trusted the HappyForms brand enough to include it in an importable starter ‘site’. Then, sadly, Theme Foundry began cutting up the plugin. Every update saw another chunk of HappyForms surgically excised; the price became prohibitive; and trust in the team behind the plugin plummeted with each successive update.

Theme Foundry deserved to make money from HappyForms. This plugin did forms the right way. Another form will take its place. It is sad.

Theme Foundry created a great product but then ruined both the product and trust in the Theme Foundry brand by choosing the wrong way to monetise the plugin. The reason this is truly deeply saddening is that someone else will run with the ideas employed by HappyForms and market their plugin the right way.

I’m not sure how Theme Foundry will regain the trust of WordPress developers but I do know it will not be easily accomplished.

There are many ways to market and monetise a WordPress plugin. Theme Foundry had an amazing head-start built within the WordPress plugin repository. I can’t believe the route Theme Foundry took.

I feel for you, Drew, I truly do. It is heartbreaking to watch all this unfold.

@thethemefoundry

For what it’s worth, we made this decision as an alternative from completely removing the free plugin from the directory.

You have pretty much removed the plugin from the directory anyway, albeit little-by-little.

Please do downgrade the free version back to version 1.7.10 then close the plugin. Tag it 1.8.11 so that existing users receive an update-to-restore-functionality notice in their WP dashboards.

Again, we’re sorry!

No you are not. Same stock line. No real sentiment behind it.

@thewebstylist Do not delete topic tags.

• This reply was modified 5 years, 4 months ago by Lee Hodson (VR51).
• This reply was modified 5 years, 4 months ago by Lee Hodson (VR51).

I completely agree. Most of this plugin’s reviews are now bogus because they apply to the earlier feature rich versions of this plugin; the versions that made the plugin useful compared to competitor contact form plugins.

The developer’s replies to updated reviews — or to any review that calls out Theme Foundry’s unethical practices — usually take the line ‘We took this heartbreaking decision because of xyz.’, or some variation of the lie. No, the decision was neither heartbreakingly nor painstakingly taken. The decision was taken because Theme Foundry realised it could get people to use the plugin then remove features from the plugin to thereby force those users to either upgrade or switch to another plugin. To be frank, Theme Foundry’s behaviour would be diagnosed narcissistic or sociopathic were it a human being.

I’m surprised this plugin is still open in the WordPress plugin repository. Other developers who pull this type of con usually see their WordPress plugin repository closed.

I think it might be time to create a fork of Happy Forms. We could call it Skippy Forms.

• This reply was modified 5 years, 4 months ago by Lee Hodson (VR51).

I’ve had this problem in the past. Items that have helped:

1) Disable web browser AdBlocker software for the site with the issue. AdBlockers block scripts required by Google Analytics.

2) Clear your web browser cache.

3) Use GADWP settings to clear GADWP’s own cache.

4) Look through your website’s plugins to find those that add features to the dashboard area (you called this the ‘cockpit’ in your question). Disable them one-by-one and reload the dashboard each time you disable one of the plugins. Do this to see whether one of those plugins prevents the display of the Google Analytics widget in the dashboard. If one of the plugins does interfere with the display of Google Analytics in the dashboard, reactivate the plugin and see whether you can disable the display of that plugin’s own dashboard widget through the “Screen Options” tab that shows at top right of the dashboard page.

One of the above 4 suggestions usually solves the problem. Hope one or more of them helps you.

Hello Dave,

I apologise for not responding sooner. The notification from this forum failed to arrive.

I will follow your advice during today.

Learning Mode made no difference. Anything else you need me me to try?

You can test for the issue internally by using WP Google Maps Pro to collect map data from Google Maps using the Google Maps API. Version 7.11.35 will be best to test with. The plugin developer added an ajax fallback in version 7.11.36 for cases where the REST API is blocked.

Thank you for your quick reply.

I have tried ‘Prevent discovery of users through WordPress REST API’ already but it had no impact.

I will see what happens when we put the firewall into Learning Mode.

This issue should be fixed by version 6.1.1 which was released a few moments ago. It works fine in the sites I’ve tested it in so far.

Same problem here using both Jetpack and Gutenberg.

Is anyone else using Social Pug? With Gutenberg enabled there is an error thrown by Social Pug. Could be coincidence.

The console output with the Gutenberg plugin enabled shows the following:

23:57:21.928 jquery-migrate.min.js:2 JQMIGRATE: Migrate is installed, version 1.4.1
23:57:22.280 index.js?ver=1562808508:1 wp.editor.withColors is deprecated and will be removed. Please use wp.blockEditor.withColors instead.
r @ index.js?ver=1562808508:1
23:57:22.945 gutenberg-image-pinterest-pro.js?ver=2.7.0:41 Uncaught TypeError: Cannot read property 'from' of undefined
    at register_block_attributes_image_pinterest (gutenberg-image-pinterest-pro.js?ver=2.7.0:41)
    at index.js?ver=1562808508:1
    at index.js?ver=1562808508:2
    at Array.map (<anonymous>)
    at ne (index.js?ver=1562808508:2)
    at index.js?ver=1562808508:14
    at Array.forEach (<anonymous>)
    at Sc (index.js?ver=1562808508:14)
    at Object.so (index.js?ver=1562808508:12)
    at HTMLDocument.<anonymous> (post-new.php:610)
23:57:22.952 timer.js:129 Started
23:57:25.921 ?v=2.0:6 WebSocket connection to 'wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data' failed: Error during WebSocket handshake: Unexpected response code: 403
g @ ?v=2.0:6
_ @ ?v=2.0:6
o @ ?v=2.0:6
00:02:15.247 jquery.js:3 [Violation] 'resize' handler took 350ms
00:02:15.262 [Violation] Forced reflow while executing JavaScript took 346ms

With Gutenberg disabled:

00:10:48.620 jquery-migrate.min.js:2 JQMIGRATE: Migrate is installed, version 1.4.1
00:10:52.821 timer.js:129 Started
00:10:53.925 ?v=2.0:6 WebSocket connection to 'wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data' failed: Error during WebSocket handshake: Unexpected response code: 403
g @ ?v=2.0:6
_ @ ?v=2.0:6
o @ ?v=2.0:6

I forgot to update this support request.

For others who might want to know:

1) Currently the only way to delete rows from the history is to delete them from the database. The history is stored in Options. The key to search for is ‘ctf_tax_history_’.

2) There is an oversight in the JS file that accompanies this plugin. The oversight prevents the Offset form field from reactivating after a conversion has completed. To fix this,

a) find the file custom-fields-to-taxonomies/js/ctf_tax.js
b) scroll to the bottom of the file and replace:

function ctf_clear() {
	$ = jQuery;
	$('#ctf_key').val('');
	$('#ctf_tax_convert .spinner').removeClass('is-active');
	$('#ctf_key').removeAttr('disabled');
	$('#ctf_tax').removeAttr('disabled');
	$('#start_convert').removeAttr('disabled');
	$('#ctf_separate').removeAttr('disabled');
}

with

function ctf_clear() {
	$ = jQuery;
	$('#ctf_key').val('');
	$('#ctf_tax_convert .spinner').removeClass('is-active');
	$('#ctf_key').removeAttr('disabled');
	$('#ctf_tax').removeAttr('disabled');
	$('#ctf_offset').removeAttr('disabled');
	$('#start_convert').removeAttr('disabled');
	$('#ctf_separate').removeAttr('disabled');
}

The plugin developer seems to have vanished. I might fork the plugin to add a few improvements. Hopefully the original developer will come back before I do that.

• This reply was modified 5 years, 5 months ago by Lee Hodson (VR51).

I’ve just realised this fault on one my sites. I’m glad you are working on a fix, thank you.

If this happens again can you please re-release the last known working version but with a higher version number than the version of the broken release? This way websites will be able to install the working version through Dashboard > Updates and the dashboard (or remote management software) will report that an update is available.

Thanks again,

Lee