Documentation explaining the changes?

Ok... I didn't mean to shout or annoy.

For the documentation - I think it would be super useful if you could describe how this module is different from setting up a flexinode content type that includes a URL field. How is it intended to be used now? Are there big secret plans down the road that will make it all make sense?

Also, I can't resist asking once again for you to please reconsider adding back the /weblink page. There is not any other module that provides this type of view. I have installed and tested every single contribution and I'm reasonably confident that this is true. This was such an incredible tool, and I know I'll have to rebuild it on my own. I think others may conclude the same thing and that your module could get forked.

I have a larger concern, which I will post in a more appropriate forum, about how many key features rely on modules that people come to rely on, such that with dramatic reversals like this people are at risk of getting stuck in an older version. I think it would have been nice for this module to be released under a new name or something since it has changed so dramatically.

Thanks much,
and I really do appreciate your work.

Best,
-Samantha

I understand your point, and I think it is true when looking at the weblink module from one perspective. But there was never anything that limited people from including weblinks with any other module - and there never has been. There was just a lack of other modules. Since 4.4 they've been popping up and that's great. It gives people more flexibility with your module and combining it with others. It has always been true, so I do not see it as anything new. The new thing is that there are a few more options now as new modules that provide for various page views are released.

But through 10+ websites where I have used weblinks, I have never enabled people to access this view of the node teaser and "visit xx" link. It doesn't suit my purposes. I want to provide a directory view of links which allows people to quickly scan the page and click to gain immediate access to any link they want. I want to be able to set this to always open in a new window. It hasn't been a big problem for it to include only web links, because my groups mostly want that to be very separate.

To me, it would have been more interesting if you had continued this directory view - and added the ability to include other node types within it. This would have offered new functionality, instead of stripping it away. Maybe it should be a separate module for some reason, but I think it is very much needed. My suggestion would be to have a directory page which is formatted exactly the same as your old directory, with the ability to choose the number of columns, whether to open links in a new window or not, which node types and vocabularies to include, etc. It should be based on a vocabulary, or maybe multiple vocabularies if desired. It would be nice if it played well with taxonomy_access, but that doesn't seem critical.

I wonder if anybody would be willing to work on it. I would if I could... and as soon as I have time to learn something new I will, if nobody has beaten me to it. I'm hoping you might consider it :)
If you have notes you can send me about this master plan, I would be happy to take a crack at writing some documentation.

Thanks,
-Sam