mungbean

Thanks, Kasia. I will look into this and mu-plugin.

Are there plans to implement the tag limit into the plugin?

Thanks for explaining the process, Adam. I am just glad your team listens and reacts to feedback.

I look forward to the repeater enhancement sometime in the future.

• This reply was modified 2 years, 3 months ago by mungbean.

Understandable, Kris. Thanks.

I’d just add that by supporting multi post creation with the repeater field group, would make the repeater function complete. And seeing as it was just rolled out, it’d be timely to add support while the feature is still fresh.

I look forward to the capability.

How does one vote/add to the roadmap?

Thanks, Patrick. I am glad others are requesting this functionality too.

Do you have an ETA on when this feature might be added?

Thanks!

Thanks. I see. That’s what I suspected (but quietly optimistic).

I’m surprised then that OG support isn’t in WP Core. Is that the plan for this plugin?

Thanks, I wasn’t aware that it was all shipped in the plugin file itself.

Would you be able to specify the sections/components/snippets that would be needed to generate a VLP from a URL? I’ll then reach out to the Pods plugin team and inquire about possibly integrating it into a Pod template.

I see. Is there a way to turn off this automated process?

As for the second part, it was based off of the assumption that a linked post was a post that contained a shortened URL. But since you said that is not always the case, this is more of a general capability request. So generally speaking, it would be helpful to have a capability to see where shortened links are used on the website. Either as a new section within the Links edit view (I can click to open/edit a link, and within it, there is a table or similar with a list of website URLs/posts/titles where that shortened link has been used), or this could be a new option in the plugin menu, perhaps “Usage” or part of Tools. There could be a use case where link updates could be applied to individual posts or to all (bulk operation)

Thanks!

Yes, thanks. I am aware of your other plugin, I’ve started some similar supported threads there. I will resume the conversation there as it appears, it’s more appropriate for that plugin rather than VLP, which has its own product philosophy.

I just wanted to follow-up on this after some further testing.

I am using VLPs both on pages and within a Pod custom post type. It appears URL Shortify can track links in VLPs on pages, but not when a VLP is within a custom post type (via text area).

Also, it appears that the links dashboard shows each instance of a link (linked post_ as a separate row, is there a way to aggregate all instances of a given link within the parent link row or its settings page?

I’d much rather have the table show all of the links I created, but then be able to manage and view where that link has been used within its settings page or table row. Essentially, being able to drill down. I feel like with the current paradigm that the table will become very crowded and unmanageable very quickly.

Thanks again!

A continuation of this topic.

You had mentioned this earlier on in the thread that the original intent of VLP was to avoid using the database and to focus on website performance. This is very logical and appreciated. But perhaps the opposite (using a database) would in effect achieve a “link manager” capability, and possibly more.

Now, this isn’t a groundbreaking idea, but in regard to a “centralized link manager” and or integrated solution, perhaps it may be easier and potentially more economical (API request-wise) to enable VLP to do both in-content (current implementation) and database/centralized. Maybe it’s a toggle where you can create a VLP in situ, or one for reuse (database). Much like how content is handled in WP already, where you create a single instance, but can reference it as many times as desired, throughout a website.

In this database/centralized use case, a VLP is created once (like a post type), the preview API (microlink) runs once to generate the preview and is stored/cached, and then the VLP instance can be referenced/embedded in content perhaps by shortcode/block/widget, where it simply mirrors the original instance. This would aid in both reducing API request burden, as well as centralize the links in one place, where they can be updated, and have any secondary references automatically reflect the update too. I’d also think that it’d be possible to track instances/where the VLP is referenced too.

Thanks!

Thanks for getting back to me. I wish their documentation was better/existed.

What plugin did you end up going with?

I found this plugin (https://www.ads-software.com/plugins/wp-file-upload/) which could be useful for adding the “change upload folder” feature. It mentions an “uploadpath” attribute. I’m not sure if it’s a code thing as I can’t see an option in settings, but I’d advise a GUI settings option rather than code.

Great!

Just for future references, for the potential link manager feature, it might be useful to look into the “uploader instances” section of WordPress File Upload plugin (https://www.ads-software.com/plugins/wp-file-upload/) settings page, as it tracks wherever the file upload shortcode is used on the site.

So from a VLP link manager perspective, you could use a similar dashboard to track VLP instances and perhaps add the ability to do bulk updates etc.