sffandom
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: WordPress 4.7.1 Breaking on Embedded Divs and JavascriptI think the problem is connected to Jetpack. I can install an older version of Jetpack that should work okay. If I still have trouble I will repost the problem in the Jetpack support forum.
Forum: Plugins
In reply to: [Search Meter] Parse error on line 665Everyone who needs an older version can download it here:
https://downloads.wp.xz.cn/plugin/search-meter.2.12.zip
And while it’s true that everyone running on an old system should upgrade, it’s not such a simple change, especially for users who are not tech savvy.
Nonetheless, as someone who needs to upgrade, I don’t want you to jump through hoops to make the new code backwards compatible. I will be upgrading soon and everyone will be safer when they do figure out how to get on newer software.
Forum: Plugins
In reply to: [Search Meter] Parse error on line 665For anyone who still needs an older version of this plugin, I was able to get version 2.12 to work.
Forum: Plugins
In reply to: [Search Meter] Parse error on line 665I’m having the same problem. I’m still using an older version of PHP for the next few weeks or months. Will have to do without the current version of this plugin.
Forum: Plugins
In reply to: [Analyticator] Really shady stuff! Please see.For what it is worth, the suspicious domains are being injected into the Google Analytics stream by a tool that creates fake traffic referrals. Most people assume it is coming from SEMalt’s nefarious botnet but there are other traffic faking tools that have been on the market for years.
You’ll have to create filters in Google Analytics to prevent those domains from being recorded in future hit reports. You can also create reports with their own special filters to remove those domains from data that has already been captured.
Although a lot of people really like the Google Analytics reporting interface it is an inferior tool that is easily manipulated by all sorts of rogue bots. At the very least you should consider using a second analytics package. Automattic’s own Jetpack offers pretty good analytics data and they filter out a lot of those fake domains. Their reports are not quite as advanced as GA’s but their interface is much easier to use.
You will also have to block some of the bad domains in your .htaccess file since those bot really do hit your Website. But the majority of the fake referral data is generated by bots that only trigger the Google Analytics Javascript without ever visiting your site.
Google Analyticator has no connection to the fake referrals.
Forum: Plugins
In reply to: [Analyticator] What Hosts does Google Analyticator Connect to?And now I have figured out the problem. I had to increase the WordPress memory limit for the dashboard widget to show up. This has nothing to do with the host being unable to connect. WordPress (or Google Analyticator) was just running out of memory and instead of reporting some sort of error it just kept waiting for the plugin to update the widget.
They had a long, complicated discussion about why they did this. What I took away from it is that the Core files are growing in total size and they are looking for ways to reduce the size of update packages. It might not make sense that they started with this one theme but you have to start somewhere. It’s an arbitrary thing.
I installed WordPress on a couple of new domains and Twenty Sixteen was there so it’s working as they want it to.
Okay, apparently the NON-installation of Twenty Sixteen on existing WP installs is a new (unannounced) FEATURE:
https://core.trac.ww.wp.xz.cn/ticket/34306
I have NOT filed a bug report. Instead, if I read that crazy discussion correctly, Twenty Sixteen will be installed for NEW Websites. Anyone who is merely upgrading will NOT get Twenty Sixteen because the development team did not want to include it in the SVN (no idea of what that stands for and I’m too sick to look it up).
I am marking this topic as RESOLVED but if I misunderstand the discussion referenced above we can re-open this discussion so people can see updates.
Well, installed the update on another site and still no Twenty Sixteen. I guess it’s bug report time because I got no response from the WordPress and Automattic accounts on Twitter.
This was a horrible update. I have been running Magazine Basic on several sites for years and have loved it. But this theme is no longer useful and I will have to replace it on all Websites.
It sounds like you may have a conflict with some other plugin. You can disable all other plugins and then reinstall it to see if that is the case.
To remove the plugin you just need to delete the folder from your /wp-content/plugins/ directory. WordPress will disable the plugin and should “forget” it.
Make sure you are using something other than the default Permalink URL before installing the plugin.
Do NOT share the login URL you create, even here, as that defeats the entire purpose of using a plugin like this.
Marking this thread as resolved.
I see. Sorry if I seemed a bit touchy. I’m just frustrated with something in WordPress right now. The wp_options table on that site has been marked as crashed two weeks in a row. It may be that the last crash affected the plugins.
Anyway, your suggested tweak worked. Thank you.
Forum: Fixing WordPress
In reply to: WP-ADMIN PAGEAre you using a content delivery network?
Forum: Installing WordPress
In reply to: Can't install WordPress onto c-panel on serverI ran into a problem like this a few months ago on a different hosting company. I was logged into the wrong Cpanel after they changed out some servers. They had to give me a new Cpanel login. Maybe you are logging into a different server than the one where your domain is actually resolving to.