Cookies are short reports that are sent and stored on the hard drive of the user's computer through your browser when it connects to a web. Cookies can be used to collect and store user data while connected to provide you the requested services and sometimes tend not to keep. Cookies can be themselves or others.
There are several types of cookies:
Technical cookies that facilitate user navigation and use of the various options or services offered by the web as identify the session, allow access to certain areas, facilitate orders, purchases, filling out forms, registration, security, facilitating functionalities (videos, social networks, etc..).
Customization cookies that allow users to access services according to their preferences (language, browser, configuration, etc..).
Analytical cookies which allow anonymous analysis of the behavior of web users and allow to measure user activity and develop navigation profiles in order to improve the websites.
So when you access our website, in compliance with Article 22 of Law 34/2002 of the Information Society Services, in the analytical cookies treatment, we have requested your consent to their use. All of this is to improve our services. We use Google Analytics to collect anonymous statistical information such as the number of visitors to our site. Cookies added by Google Analytics are governed by the privacy policies of Google Analytics. If you want you can disable cookies from Google Analytics.
However, please note that you can enable or disable cookies by following the instructions of your browser.
Visit the Wiki extensive and up to date documentation at your fingertips.
Missing images/links, any comments, suggestions, need help? Contact me
mail from a new OpenComment Developer James Friesen: I found the CVS code. I realized that you have that in there as a branch of com_akocomment. I was mislead because the project still has the old name. I found the opencomment code but I need to know what versions are which. I see that you are already working on a version for Joomla 1.5.x but I are you also planning to finish the version for 1.0.x? I don't think I'll be upgrading to 1.5 for a while so I'm interested in making the 1.0.x version work. I connected to the CVS repository. I see that each regular Joomla folder as a akocomment and opencomment version underneath it. What's unclear to me is how to manage the different versions (for 1.0.x and 1.5.x) and how to run the latest version of OpenComment on my test server. If you can offer some tips that would be helpful.
In fact I have still not found a correct solution to the problem of PHP versionning under PHPEclipse
I don't want to version joomla together with a database for each component i develop...otherwise I will have to version 5Mb (joomla) + database (or delta) + my component.
PHPEclipse (or eclipse) only make CVS version at the project level...it refuse to check in a directory (a component or module for example) in a project
I really need to ask some people on Joomla Forge, and find a solution to that issue.
OpenComment has been develop under Joomla 1.0.8, it was working but was not fully tested...This code has been tagged and closed in a CVS version: v01_00_00 The CVS HEAD contains the code for the 1.5.x version of Joomla. If You want to continue version 1.0 You'll need to open a CVS BRANCH of the version v01_00_00
How to join the development?
You need to install Eclipse 3.1.1 and the plugin PHPEclipse (PHP eclipse do not run under 3.2Mx)
You need to install the latest JDK to run Eclipse,
You need to try to install the PHP debugger.
You need to install MySQL4
You need to install a Joomla 1.0.8 version or Joomla 1.5.X version
You need to be accredited y me to have a commiter access to CVS
As You see a lot of things to do before ever being able to write code. In order to help You, I have decide to open:
A new project at Joomla Forge (It must be accepted first by the forge)
I found another project which aimed at the same result:
I've decide to join the team of !JoomlaComment and help Alain and Daniel continuing the development. Right now I will try to reduce the spamming attacks I've encountered in the last few days (250 comments entered by a bot) First step is to review the code in order to avoid replaying attacks by request forgery (saving an attack vector with a specially hand crafted URL), After that I will join my effort to Alain and Daniel and try to …
OpenComment is not DEAD I will be reading some sources My forum forums.waltercedric.com Joomla! Extensions OpenComment reviews Joomla! forums during the week seeking for bugs and new functionalities you are requesting. So this is your chance! Keep cool, and be descriptive ;-) …
XAJAX team has release a new version of its library for PHP and ajax: XAJAX 0.2.5xajax 0.2.5 has been created as a bridging step to xajax v0.5. xajax 0.2.5 aims to be forwards and backwards-compatible with xajax versions, while at the same time providing important security updates that have been lingering around in the xajax codebase for a whileIt's been just over one year since we released our last version of xajax and it was about time we released another …
opencomment 3.0.30 NEW: you can disable the paging algorithm... so users do not have to click many times to go through all commentsNEW: admin can unpublish comment in frontEndNEW: more security check for admin AJAX functionsBUG: language not correct in frontend, fallback to english. was only if register globals offBUG: newest comment first fix ... submitted by FannoBUG: bbcode support fix ? submitted by FannoBUG: small admin fix submitted by FannoBUG: IMPORTANT FIX do not allow visitor to delete comment …
It will be a huge patch release this time. Let me first start with the new features list...NEW: Search contains the word "search" now as default.NEW: Following rules apply now to the form field "Name":If a user is logged in, he can not change his nameIf a guest is around, he can change his name only if the admin settings "name field: No Yes Is the field name read only?" is set to NONEW: Avoid logged in user to rate …
The code is getting better at each release...but may have encounter some regressions. So Your feedback is welcomedNEW: use the project xajax-joomla.org which let you run multiple XAJAX modules or components (1)BUG: encoding problem should be defacto solve as XAJAX now use Joomla encoding NEW: Version able to run on hardened PHP server: Register globall OFF (php.ini) + SAFE_MODE On (php.ini) + RG_EMULATION = 0 (Joomla globals.php). Should solve different issues like "You are trying to hack me"BUG: User homepage …
The list of corrections...NEW: full german translation courtesy of Joern Gerken successwiki.comBUG: can not update value of opencomment_cleanupPostingUsersHistoryfromDatabaseAfter (default was 10 minute)BUG: \r\n and/or \n (Newline) were not translated into <br />BUG: The openComment menu shows an entry called "editOpencommentCSS", which does the same as "Edit newpost feedback template".OPEN: Warning: mysql_errno(): supplied argument is not a valid MySQL-Link resourceI can not reproduce it on XAMPP 1.5.4a ( Apache 2.2.3 - MySQL 5.0.24a - PHP 5.1.6 & PHP 4.4.4 ) with …
A minor release because a lot of thing need to be done behind the scene....NEW: AJAX Encoding can be freely defined by user. This is a temporary solution, ideally it must be read from Joomla Language file.BUG: the "write comment only visible for first article" is solved.BUG: fully translated Administrator panel and localized in English.php. File now contains 370 keysSoon:PENDING prio1: Ajax problem still persist that it did not work with Jim IM and whosonlineext modules. it will be soon …
The component OpenComment is under heavy testing, a big thanks to all users posting bugs report in the Bug tracker ForumsNEW: Search function in query control panelBUG: Found latest error in installer fileBUG: No more <? starting tag but <?php was revealed by users using PHP5 and Magic_Quote = OFF in PHP.iniBUG: Solve small bugs in administrator panel.NEW: A new settings: Users Posting History, how long a user can not submit a new comment in the same article This do …