картинка классная. люблю такие штучки-обводки
Там вся верстка очень продуманная
Vladimir
Vladimir
Шрифт мне понравился
Evgenii_Web
по мне так у меня верстка лучше 😂
Sergey
WT Articles anywhere with fields v.2.0.0
Контент-плагин Joomla, позволяющий вставлять информацию из материалов и пользовательских полей материала в любом месте, где работают контент-плагины с помощью шорт-кода вида {wt_article_wf article_id=XXXX tmpl=XXXX}. Для плагина возможно (и даже необходимо) создавать свои макеты вывода, которые Вы указываете в шорт-коде.
Что нового?
- Структура плагина обновлена, с учётом требований Joomla 4. Это означает, что плагин будет работать и на Joomla 5.
- Добавлен плагин кнопки редактора для более удобной вставки материалов и выбора макетов.
- Добавлен новый макет вывода link, который представляет собой ссылку на материал с его названием. Если Вы измените название материала - оно автоматически изменится.
- Минимальная версия - Joomla 4.3. Это связано с использованием namespaces для плагинов группы editors-xtd.
Скачать плагин
======================================
WT JoomShopping Last Seen products v.2.0.0
Пакет, состоящий из модуля и плагина. Плагин записывает в cookie просмотренные посетителем товары, а модуль отображает их. В плагине настраивается время жизни cookie - сколько дней хранить в браузере пользователя информацию о просмотренных товарах. Это бесплатный аналог аддона "Addon last visited products" от MAXXmarketing GmbH (разработчиков JoomShopping).
Что нового?
- Пакет расширений адаптирован к новой файловой структуре Joomla 4. Это означает, что он будет работать и на Joomla 5.
Скачать расширение
Sergey
Vladimir
Vladimir
Добро пожаловать в дружелюбный чат Joomla
Vladimir
https://partnerkin.com/blog/stati/antik-sravnenie-brauzerov
Vladimir
Антидетект-браузеры в 2023 году: популярные продукты, автоматизация процессов
Сегодня запуск без антика невозможен не только в арбитраже, но и во многих других нишах. Например, антидетект-браузеры активно используются в крипто-торговле, SMM и других направлениях. На рынке есть несколько известных антиков и с десяток менее известных, а споры о том, какой выбрать для работы, можно сравнить со спорами между владельцами iOS и Android.
В битве за каждого клиента, антидетект-браузеры уже не только маскируют ваш цифровой отпечаток, но и умеют многое другое:
🔘 Нагуливать куки;
🔘 Автоматизировать простые процессы;
🔘 Позволяют настраивать командный доступ;
🔘 Дают возможность быстрого импорта и экспорта и многое другое.
Мы провели ресерч, среди популярных антидетект-браузеров и бонусом рассказали, как автоматизировать фарм аккаунтов в Dolphin без ZennoPoster или BAS. Кто выиграл в битве антиков и можно ли автоматизировать фарм?
Sergey
привет может кто настраивал com_komento в j4. где там выбирается шаблон? для тройки все понятно а вот в 4 не вижу
hary
обьясните как можно поставить 5 джумлу? создал тест сервер на хостинге, дополнительный сервер баз данных мариядб 10.8 - и там адрес не локалхост, а айпишник. как джумле то показать его?
hary
Не удалось подключиться к базе данных: Access denied for user 'user'@'localhost' (using password: YES).
Дмитрий
Дмитрий
на данном этапе
Дмитрий
зачем ее смотреть? если нужен код, то все на гитхабе
hary
я то об этом не знаю, думал что внешне меняется. вот и хотел затестить
RINAT
я то об этом не знаю, думал что внешне меняется. вот и хотел затестить
Внешне его не поменяли
Это просто дароботка текущего
hary
о. вышдло наконец. нужно было правильно указать имя хоста. поперебирал настройки в исп панели. и наконец вышло
Sergey
я то об этом не знаю, думал что внешне меняется. вот и хотел затестить
Пока ещё нет. Объявляли типа конкурса дизайнеров, обещали как минимум цветовую гамму другую
Eugene
@sergeytolkachyov Серег, а как там дайджест? летом выпустишь?
RINAT
Пока ещё нет. Объявляли типа конкурса дизайнеров, обещали как минимум цветовую гамму другую
Он про joomla 5,
А не основной сайт 😊
Sergey
Nicholas Dionysopoulos
Something is rotten in the kingdom of Joomla!.
https://elts.joomla.org promises paid (“just” 90 Euros a pop) extended long term support. However, it is not directly offered by OpenSourceMatters, Inc (the legal entity of the Joomla! project). It's offered by djumla GmbH. Who is djumla GmbH? According to https://www.djumla.de/impressum it is David Jardin. If that name sounds familiar, it's because he's the Joomla Security Strike Team team lead: https://volunteers.joomla.org/joomlers/67-david-jardin
So, let me spell it out for you. Security researchers report vulnerabilities for Joomla 3 to the Joomla Security Strike Team (JSST), without receiving a bug bounty. The JSST lead then makes security fixes which he only releases to his clients for a fee.
There are several problems with it.
First of all, this reflects badly on the impartiality of the JSST. If JSST's privileged information and work product are to be used by _one specific_ company why would a security researcher report security issues _without_ expecting a bug bounty? Why would any unpaid JSST member contribute their _unpaid_ time to resolve security issues, only for the team lead's company to take this work product and sell it for profit? This will short-circuit the operation of the JSST and put every single one of us in direct and immediate danger.
What stops the team lead's company from using the privileged information it has acquired to compete with third party developers making security products for Joomla? David Jardin kicked me out of the JSST because I had already written code to protect against a Joomla 0-day in 2015, even though the code was written 5 years prior to report to the JSST, and the improvements to that code were written a week before the report to the JSST. But I digress. This is exactly why this kind of behaviour is expressly forbidden by the [Joomla! Code of Conduct](https://www.joomla.org/about-joomla/the-project/code-of-conduct.html). This is what it has to say about Conflict of Interest:
“When using Project resources or making decisions within the board, your department, team, or subteam or the concerning Project's policy positions, you must do so based only on the best interests of the Project and its user community. If you have a situation or affiliation that might constitute or lead to a conflict of interest or might be perceived by a reasonable person in the community to be a conflict of interest, disclose this to your Team Leaders or the team as a whole. If appropriate, after discussing with your team, you should remove yourself from specific decisions or discussions in which you may have a conflict of interest.”
The ELTS initiative —in other words, giving David Jardin's company a _carte blanche_ to make money out of privileged information he receives as the lead of the JSST— under a project initiative awarded in opaque, entangled, morally corrupt, and potentially illegal circumstances could have NOT been approved without being discussed in the board meeting of OpenSourceMatters, Inc. Sitting on the board is Harald Leithner, the Operations and Production departments' coordinator. The JSST is under the Production department. So, either David never told Harald about the COI (hard to believe since Harald, being Austrian, knows exactly who djumla GmbH is — it's a very well known company in the Germany - Switzerland - Austria area), or they think we are all idiots. Obviously it's the latter. It is also truly bizare that Harald, the release lead of Joomla! 5.0, would agree to such a late decision —less than a month before the official End of Life for Joomla! 3— which undermines the release he's leading. What exactly is going on here?
Sergey
If the project intended to do this all along, why not announce it in advance? Why not have JSST —the same people it has now positioned to make money out of this— provide security patches for Joomla 3 for another 18 months as is their mandate? If they really wanted to offload this work from JSST, why was there not a RFP process which would have allowed third parties without a Conflict of Interest to participate? If the JSST information and work product is not to be considered privileged and beyond the reach of a commercial entity, why then not share it with all of us third party developers who are publishing security extensions for Joomla? This all screams “cronyism”. This is what mafia-states do: they award lucrative contracts to their favoured oligarchs and screw the people.
Beyond that, the tergiversation surrounding the Joomla 3 support is very confusing to Joomla's users and undermines the Joomla! release strategy. Why would anyone move away from Joomla 3 in the next 18 months? Maybe the Joomla project will make another ELTS extension. This will create a ghost fleet of Joomla sites running on increasingly ageing —therefore vulnerable— PHP and web server versions, increasing the chance that they will get hacked with everything that entails to the reputation of Joomla as a whole.
It also makes users of Joomla 4 think that there is no reason to migrate their sites to Joomla 5. Joomla 4.4 is anyway supported until October 2025. Maybe there will be an ELTS for Joomla 4, too, extending the support to February 2027, nearly the end of the Joomla 6 release (as per the roadmap). This creates a massively fragmented landscape of Joomla sites, running in drastically INCOMPATIBLE with each other versions of Joomla, which has a direct negative impact on third party extension developers. It also makes it especially difficult to migrate sites, unless us 3PDs maintain “bridge” versions of our software for 6 years at a time. To give you an idea of how unlikely this is, we have published over 150 releases of Akeeba Backup across five major versions in the last 6 years. The only way to do that would be _NOT USING JOOMLA FOR OUR EXTENSIONS_, each one of us third party developers reinventing the wheel, and creating an even more fragmented landscape that makes site integrators' lives impossible, leading them away from Joomla. How the heck does that help Joomla?!
Beyond that, this is a stab in the back of third party extension developers. [Months before the official Joomla 4.0.0 release](https://magazine.joomla.org/all-issues/november-2020/joomla-3-10-status-release-strategy) we were told that Joomla 3.10 was a bridge release. [On release day](https://magazine.joomla.org/all-issues/august-2021/joomla-3-10-end-of-support-handling), we were told in no uncertain terms that Joomla! 3 moves to End of Support (i.e. End of Life) on August 17th, 2023. Messages in Joomla 3 itself communicated the same message the past two years, in an increasingly urgent tone. We planned our releases and product roadmaps on this timeline. A timeline they promised was to be trusted in https://www.joomla.org/announcements/release-news/5868-joomla-5-panta-rhei-the-follow-up.html . Now they come and tell us, once again, that the Joomla Project's leadership CANNOT BE TRUSTED.
Sergey
They expect third party extension developers to turn our product release roadmap on a dime, at the end of July, and offer another 18 months of support to our Joomla 3 software which we've planned to move into End of Life or security maintenance as per their original timeline. They expect us to maintain extensions for _three_ major versions of Joomla, incompatible with each other: Joomla 3, Joomla 4, and Joomla 5. This has a tremendous impact on the viability of our businesses, and whether we can realistically support Joomla 5 once it is released. This was all done without any consultation with us third party developers. As things stand, there is no third party extension developer who can afford to maintain three branches of the same product across three completely incompatible versions of the Joomla CMS. This will lead to 3PDs making one of the following decisions:
* Only support older versions, never the newest one. This undermines Joomla's release strategy as it leads to Joomla versions lacking important extensions for completing a site build for years, therefore leads to new sites being launched based on _old_ versions of Joomla.
* Only support newer versions, making older versions of their products for LTS / ELTS versions of Joomla obsolete. This means that older sites will end up running _for years_ older, potentially insecure code with everything that entails about these sites getting hacked and the reputation of Joomla as a whole.
* Only actively support newer versions, while selling expensive ELTS for older versions. This will increase the total cost of ownership of old sites to stratospheric levels. This requires site integrators to spend an exorbitant amount of money to support older sites that they had not planned when selling the site, or force them to run old, potentially insecure code for years with everything that entails about these sites getting hacked and the reputation of Joomla as a whole.
There is no scenario in which the people we are building Joomla for, its end users, reap any benefit. It mathematically leads to further erosion of the Joomla installed user base and the imminent collapse of Joomla as a viable PHP FOSS CMS. It is incredibly saddening to see that the Joomla project decided to destroy itself, just to give a kickback of a few dozens of thousands of Euros to its inner circle.
This is wrong. This is destructive. This is completely against the values of Free and Open Source Software.
Joomla's leadership has firmly declared that the Code of Conduct is perfunctory, only to be used as a weapon to purge those who disagree with the disastrous decisions of the leadership.
Joomla's leadership has firmly declared that the third party developers and contributors, on the hard work of which this project owes its success, mean nothing to them.
Joomla's leadership has firmly declared that they are willing to operate as a corrupt organisation, giving kickbacks to each other in an opaque, morally bankrupt, and legally questionable manner.
17 years ago it was exactly this lack of morality which led the project founders to fork from Mambo. This is what led to the formation of Joomla! with the tag line “…because Open Source matters”.
Open Source still matters. The current leadership has lost its way. The current leadership has been corrupt by the illusion power and feedback loop afforded by the current, perverse structure. This is something we _knew_ would happen. I had warned about that nine years ago and proposed how to fix that: https://www.dionysopoulos.me/refactoring-joomla.html (before the restructure was finalised) and https://www.dionysopoulos.me/the-problem-is-the-vision.html (after the restructure was finalised).
The current Joomla leadership needs to go.
Every. Single. One. Of. Them.
(And yes, I do count my wife in the people who need to go. She was on the board meeting which approved this catastrophic nonsense and she bears responsibility as President of OpenSourceMatters, Inc.)
The entire leadership is tainted.
Sergey
This project needs to start with a clean slate, embracing meritocracy, and the Free and Open Source Software ethos.
If the leadership is unwilling to step down then the community needs to step up. There are no dead ends in FOSS. If it's not working, you fork it, and you fix it.
Sergey
Vladimir
Какой раздел ?
Sergey
Какой раздел ?
https://joomlacommunity.cloud.mattermost.com/main/pl/7rkwcjmu8iyr7mu1ajgqm6ttdw
Eugene
а можно без этой простыни долбанной? что не так?
Eugene
переложите на нормальный язык, минуя воду, в двух словах
Vladimir
а можно без этой простыни долбанной? что не так?
Короче создали компанию которая за деньги будет поддерживать Joomla 3
Vladimir
И создал ее глава jsst
Eugene
а кто оплачивает банкет?
Eugene
типа, Joomla 3 не будет иметь EOL через месяц?
Vladimir
типа, Joomla 3 не будет иметь EOL через месяц?
Будет. Но для всех остальных - за деньги продолжится поддержка
Vladimir
Как в винде
Sergey
В общем, с ним не поделились, называется
Vladimir
В общем, с ним не поделились, называется
Ну тут идея в том что используется служебное положение
Vladimir
Вот о чем он
Sergey
Мол, он раньше имел доступ к данным департамента безопасности и это позволяло ему откручивать платные услуги своей компании до того, как будет выпущена заплатка в ядро. Его выгнали из департамента вследствие конфликта интересов. Теперь тем же самым занимаются другие 2 чувака, и Николас говорит, что им не выгодно будет развивать Joomla 5, так как они будут терять на этом деньги. лучше развивать старый плохой продукт и драть деньги за поддержку.
Sergey
С женой у него там конфликт из-за этого )
Sergey
Санта-Барбара прям
Dmitriy
(And yes, I do count my wife in the people who need to go. She was on the board meeting which approved this catastrophic nonsense and she bears responsibility as President of OpenSourceMatters, Inc.)
Ну ночует он сегодня не дома точно 😊
Sergey
Sergey
Sergey
Надо скачать, пока не поздно
Sergey
(And yes, I do count my wife in the people who need to go. She was on the board meeting which approved this catastrophic nonsense and she bears responsibility as President of OpenSourceMatters, Inc.)
Ну ночует он сегодня не дома точно 😊
Vladimir
У него кажется это периодически случается
Vladimir
Дмитрий
=)))
Igor
Я вот только не понял, они олпять что ли релиз j5 сдвинули. А j4 и j3 уделенили?
Vladimir
Я вот только не понял, они олпять что ли релиз j5 сдвинули. А j4 и j3 уделенили?
Не. Предложили поддерживать тройку за деньги
Vladimir
https://elts.joomla.org/
RINAT
Че там еще интересного😊
RINAT
Пока единому не пришли?
Он сегодня будет ночевать дома?😄
Vladimir
С мобилы ссылка не открывается в приложении
Sergey
Town square