Bastbra
Forum Replies Created
-
Forum: Plugins
In reply to: [SEOPress - AI SEO Plugin & On-site SEO] SEO metabox disappearedYeah, but it doesn’t seem they are related to SEOPress. Only this one occurs when I open the bar: “36px default size for wp.components.FormTokenField is deprecated since version 6.8 and will be removed in version 7.1. Note: Set the
__next40pxDefaultSizeprop to true to start opting into the new default size, which will become the default in a future version.”Forum: Plugins
In reply to: [SEOPress - AI SEO Plugin & On-site SEO] SEO metabox disappearedI checked this section, but I never clicked administrator (the account in use) out. So the boxed are already unchecked (so it’s not preventing anything from showing). Still I can’t see anything.
Also tried checking it in, and then out-checking it. But I can’t edit anything, with the one and the other option. It’s still missing completely.
Forum: Plugins
In reply to: [SEOPress - AI SEO Plugin & On-site SEO] SEO metabox disappearedYeah, I can see this with something like “has some issues”. But when I click on it, the big box opens and I can only see the problems and no “fixing”, so I cannot edit anything there. It’s just the SEO problems, without fields to edit.
I have the newest version, tried rollback to older version to fix, but that also didn’t work.
Oof, I misread that thinking that MUST have been the option to export it, without looking at it close enough, after reading your message about the other user fixing it with that. I have backups, but I don’t think they will be useful for this, since it is still not working.
I did exactly what you said, I “deleted the plugin and all the data and then re-installing IA and importing the data back in” with your settings page “export/import” feature.
- This reply was modified 1 year, 6 months ago by Bastbra.
You did not ask for the debugging info. This is new information right now. Also, you said you could do this with the database and recommended doing this in the plugin itself, because one user did this and it worked. I did not touch the database, I just used your plugin to export and import again after reinstalling. And yeah, the export file was broken, too. Please be truthful now. You never said you would export the file IN the plugin for me.
Forum: Plugins
In reply to: [Independent Analytics - WordPress Analytics Plugin] Analytics aren’t loadingOkay, I did this in wp-content/plugins/independent-analytics/temp/, since I don’t use the Pro version. Still, it did not work.
Forum: Plugins
In reply to: [Independent Analytics - WordPress Analytics Plugin] Analytics aren’t loadingI need the other plugins, reinstalling and installing again did not work. Also the plugin is not counting correctly anymore, it shows wrong data for the last few days. I don’t know what you changed, but I can’t use the plugin anymore, if this error is not resolved :/
@timse201 You can try to delete the plugin via web ftp from your plugins list. That’s the only way if you don’t have an option to access via Jetpack for example. It will lock the entire admin area and it is not possible to update the plugin from there again.
I will not use Security Ninja again. If this should protect a site, but locks it without any chance other as by luck to regain access, I’m finally not into it anymore.
Forum: Plugins
In reply to: [VG WORT METIS] Fraglich, ob Plugin tatsächlich zähltDas heißt, dass das Plugin permanent schaut, ob ein Text lang genug ist oder nicht und entsprechend meldet? Oder zumindest bei jedem Update des Textes?
Komischerweise werden wir im METIS keine URL-Daten angezeigt und kein Artikel hat den Mindestzugriff erreicht, dabei müssten es schon sehr viele sein, wenn ich die Statistiken aus Deutschland auswerte – dicke genug, damit auch METIS das anzeigt. Jetzt habe ich die Sorge, dass bisher alles für die Katz war, obwohl es den Mindestzugriff schon hätte geben müssen.
Thanks a lot! Did that.
And if I generally want to get rid of the /? in search results, should I just add “?” without something behind it? Most of the wrong results are with ?amp and ?quad_cc, but a few are also with different things behind this.
Best regards!
Hi, it is Site Kit specific. How can I remove those anchors ads above in Site Kit? For me at the bottom is enough and the guide did not help me. I tried to do it with the preview tool, but it did also not work.
I asked the only other plugin that could cause it and they said this is a Site Kit issue. So yeah, I’m stuck here.
Hi,
I tried that a bit now, but in the preview the error does also not occur, which is already weird. It just happens to be on the mobile version of the “real site” with ads.
So I looked if there are placed ads in the header slot, which sometimes seems to happen in the desktop version (but is not making problems there) and could also infect the mobile version, even if I can’t see it. Unfortunately, in the ad preview this slot is not marked. If you look at the desktop version, it is placing them in the dark header, so it’s pretty obvious that there has to be some kind of placeholder.
I don’t know if Anchor ads are the problem, since they are at the bottom, but of course they could have an impact. I will deactive them for a time frame, but of course I don’t know if this is really the error – I kinda doubt it. And of course this is making a strong impact on ad revenue, fixing it without deactivating features like anchor ads would maybe be better. But somehow there must be a way to fix this issue, which really seems to be caused by auto ads.
Best regards!
Hi, thanks a lot of your answer.
It seems the plugin did not cause the database errors, that seems to be something different – although I still don’t know what.
I will send you more information on the case with the problem as soon as I am able to, at the time I deactivated it. With Query Monitor I was able to track this down, so I thought this would be the issue I was searching for, but even if it certainly is an issue, it does not seem to be that problematic to cause more. Thanks also for your clarification!
I will try to search more, get more details of this issue (maybe this is just something with Query Monitor and not really a problem), and hopefully find the actual problem that I am searching for right now.
Best regards and thanks for your effort so far!
Exact same error here, would be great to fix this soon, it is kinda annoying and also not great for Google Analytics.