C0Rrupt
Beginning Developers
This space is for newcomers, who wish to build a new plugin or to customize an existing one to their liking
Feedback and Planning
Discussions about the past, present, and future of Elgg and this community site.
Elgg Technical Support
Get support from other Elgg users
Plugin Development
Talking about how to write plugins
C0Rrupt replied on the discussion topic Mods as Plugins- C0Rrupt replied on the discussion topic Mods as Plugins
- C0Rrupt replied on the discussion topic Mods as Plugins
Nearly two years ago
This was discussion about community Ui not about plugins.
This is reminiscent of my concern about plugins. Besides, aren't all mods plugins? Shouldn't all mods be plugins?
What plugins are you talking about?
All important plugins are supported by the few developers who are on Elgg.
The rest of the unsupported plugins have either lost their relevance or are not needed by users.
If the developer abandoned the project, why would anyone work on it?
iionly wrote a good post about this problem, please search the community for similar whiny discussions ("Elgg is dying ... blah blah blah")
If you can't find the plugins you need here, look for them in the repositories on GitHub or somewhere else.
We created a channel in Telegram, where we regularly posted information about the release of all plugins from all sources, both paid and free.
P.S. Why do you call plugins "mods"? There are no mods in Elgg, only plugins.
I call plugins 'mods' because they're modules in the 'mod' directory, along with many core functions. I thought that it would be sensible for all functions that operate as modules to be modular. Your response is disheartening, especially as such a cold dismissal of a reasonable suggestion from a long-time elgg enthusiast. My suggestion is good-natured and well-intentioned. It's not whiny. But it does disincline me from contributing back to an uninviting, insular community who seems to not want my contribution.
I call plugins 'mods' because they're modules in the 'mod' directory, along with many core functions. I thought that it would be sensible for all functions that operate as modules to be modular.
"All important plugins are supported by the few developers who are on Elgg. The rest of the unsupported plugins have either lost their relevance or are not needed by users." ignores both the example that I provided and the need that I expressed. I wish you wouldn't be so dismissive in the face of direct evidence to the contrary.
Your response is disheartening, especially as such a cold dismissal of a reasonable suggestion from a long-time elgg enthusiast. My suggestion is good-natured and well-intentioned. It's not whiny. But it does disincline me from contributing back to an uninviting, insular community who seems to not want my contribution.
- C0Rrupt replied on the discussion topic HTML DOM Parser Plugin
- C0Rrupt replied on the discussion topic HTML DOM Parser Plugin
- C0Rrupt replied on the discussion topic HTML DOM Parser Plugin
@ihayredinov
I'm sure many here happy to see you alive :)
@ihayredinov
I'm sure many here are happy to see you alive :)
Ismayil (@ihayredinov),
So good to hear you're still alive. I didn't think I'd ever have a chance to say how grateful I am for your work those many years ago. I'm still using several, including, now, hypeScraper. I convinced it to do what I needed, for the most part, but am still bedeviled by its difficulty scraping pages from several different domains. Here's an example: "Parser Error for HEAD request (https://www.walgreens.com/store/c/onetouch-ultra-2-blood-glucose-meter-kit/ID=300400575-product): cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)" because "filter_var($url, FILTER_VALIDATE_URL))" returns false. If you have an inspiration for where to look for a solution, I'd be incredibly grateful.Sincerely,
- Scott (@C0Rrupter)