pharmanext
Forum Replies Created
-
Forum: Plugins
In reply to: [Ad Inserter - Ad Manager & AdSense Ads] HTML selector windowHmm, how interesting. Thanks for the tip.
No errors in the console.
Perhaps some interference from the theme or plugins. I will look into it.
Sorry for the inappropriate claims about the quality of the plugin.Forum: Plugins
In reply to: [Ad Inserter - Ad Manager & AdSense Ads] HTML selector windowPerhaps you didn’t quite understand me, or I didn’t describe the situation well.
For a start, see the screenshot.
As you can see the HTML element selector window takes up two thirds of the browser window.
Obviously, it looks pretty bad from the usability point of view.
Since the plugin has this feature, why not make it more usable? Why is the selector so gigantic? It doesn’t make any sense.
As I said earlier, because the HTML element selector window overlaps the top of the page, it is impossible to scroll all the way to the top to pick a selector in the header.Forum: Plugins
In reply to: [Ad Inserter - Ad Manager & AdSense Ads] Rotation LogicThanks for the information.
However, imagine that there are 20 blocks, each with its own and different code_main. In other words, the code load and complexity increase.
That’s why I think it makes sense to consider what I said above about the code_main being before the separator shortcode
[ADINSERTER ROTATE]should always be inserted and not involved in the rotation process.Do you think this is a healthy idea?
P.S. The logic I suggested for
[ADINSERTER ROTATE]is already used in[ADINSERTER VIEWPORT]: If you put code above the first VIEWPORT separator it will be inserted for all viewports. See https://adinserter.pro/documentation/device-detection- This reply was modified 3 years, 6 months ago by pharmanext.
Forum: Plugins
In reply to: [Ad Inserter - Ad Manager & AdSense Ads] Insertion after a random paragraphThanks, it works fine.
However, it is not possible combinations like
[1-3], 4, 5, so that the block is inserted randomly in the interval1-3and necessarily in position4and5.Forum: Plugins
In reply to: [Ad Inserter - Ad Manager & AdSense Ads] Insertion after a random paragraphThank you for your reply.
Also, as an option, for randomization you can consider not only structures with a range of paragraphs (e.g., 3-10), but also structures with a list of paragraph numbers (e.g., 3, 5, 8), or mix of two types of structures.
- This reply was modified 3 years, 7 months ago by pharmanext.
Forum: Plugins
In reply to: [Ad Inserter - Ad Manager & AdSense Ads] Viewports settingsI made a new Viewport named Test and
min width1280 px.
https://ibb.co/fFk4587In the block I set the following code:
[ADINSERTER VIEWPORT="Test"] TestWhen the Preview button is pressed with a screen resolution of 1280 or more, Test is output as it should be.
When I press the Preview button at a screen resolution less than the minimum 1280, Test is still output, although it shouldn’t be. Does this mean that the new Viewport is not working properly, or am I doing something wrong?
Forum: Plugins
In reply to: [Ad Inserter - Ad Manager & AdSense Ads] check bugThanks a lot!
Forum: Plugins
In reply to: [Schema & Structured Data for WP & AMP] PaywallThank you for your reply.
Paywall support would be a great feature of your plugin. Looking forward to it.
Forum: Plugins
In reply to: [Schema & Structured Data for WP & AMP] PaywallWell, look, let’s imagine a situation where all the posts are behind the paywall. Accordingly, if a search bot, which has the right to access the full version of the posts (such right should be granted to it for SEO purposes), will index the posts, he will face a dilemma. On the one hand, he sees the entire post (as if he were a registered user), on the other hand, he sees only part of the post (as if he were an unregistered user). Hence the need to improve the schema properly.
Forum: Plugins
In reply to: [Schema & Structured Data for WP & AMP] PaywallPerhaps I didn’t put it quite right. But the point is to show the search bot the entire post as it is seen by the registered user. Otherwise it turns out that the search bot sees only a tiny part of the content, because the entire post is hidden behind the paywall, and therefore the position in SEO simply collapses, because there will be little content in the search index. That said, if the search bot sees the entire post, but an unregistered user only sees part of the post, there is a cloaking issue. It seems to me that your plugin may well solve it. See https://developers.google.com/search/docs/advanced/structured-data/paywalled-content
Forum: Plugins
In reply to: [Schema & Structured Data for WP & AMP] PaywallThank you for your reply.
The capabilities of Leaky Paywall plugin are really impressive. However, such extensive functionality is hardly needed at this stage.
I would only ask you to add full and universal paywall support to Schema & Structured Data for WP & AMP as recommended by Google and without any linkage to third party plugins. That would finally solve the cloaking issue.
Forum: Plugins
In reply to: [Schema & Structured Data for WP & AMP] PaywallThank you for your reply.
The first step would be to implement a lock for all posts. Each post is available to the unregistered visitor, but only part of the content of each post is shown, such as the first 35% of the text. I think this is reasonable: The visitor should see and understand what the post is about. Next, a free sign-up is offered. After that, full content of all posts becomes available. And this is where the cloaking issue comes in. See https://developers.google.com/search/docs/advanced/structured-data/paywalled-content
Forum: Plugins
In reply to: [YARPP - Yet Another Related Posts Plugin] YARPP PortionsMay I ask you to answer my question?
Forum: Plugins
In reply to: [YARPP - Yet Another Related Posts Plugin] Force PostsMay I ask you to answer my question?
I probably didn’t express myself correctly, sorry. I’d like to know which JS and CSS that WP External Links uses (e.g. wpel-link-highlighter.js) I can try to turn off from speed optimization to maybe make things work. It’s possible that Ezoic is optimizing these files and that’s why the plugin doesn’t work.