Welcome, Guest. Please login or register.
Did you miss your activation email?
Oct. 13, 2015, 09:36:42 AM
56819 Posts in 12813 Topics by 24848 Members
Latest Member: dualf
  Show Posts
Pages: [1] 2 3 ... 49
1  General / Prado-powered Applications / Re: coinsville.com - Coin catalog & collector app on: Jan. 11, 2013, 11:54:53 AM
Added your site to the list of featured applications Smiley
2  General / Announcements / PRADO 3.2.0 is released! on: Jun. 25, 2012, 04:40:39 PM
The PRADO Team is proud to announce the formal release of PRADO 3.2.0.

A lot of time has passed since the release of PRADO 3.1.0 in july 2007, and a lot of things happened to the project: part of the old development team moved to other projects, and new members got in to form a new team.
Meanwhile, PRADO 3.1 received ten minor releases to ensure proper PHP compatibility, fix bugs and add more controls; but the real development was happening on another branch.

Today we uncover the fruits of this development: while keeping major compatibility with previous PRADO versions, the fresh new 3.2 brings some big improvements:

Better performance:
  • Bottleneck code has been rewritten or modified to make use of new PHP capabilities to work faster
  • Progressive rendering is now possible, ad-hoc code can lower considerably server memory usage
  • Better caching of Javascript files decreases server load
More security:
  • The Javascript related code has been reworked to ensure better protection from XSS attacks
  • Dozens of bugs have been killed from the framework
More power:
  • Active controls can be created in an Ajax callback, and their Javascript dependencies inclusion will be worked out automagically
  • Active controls usage is simpler, since they now follow strictly their non-active counterparts behaviour
  • A lot of new controls have been added
  • All of the controls are documented with working examples
Many minor feature enhancements and bug fixes:
While the HISTORY file itself lists more than 60 major bugfixes and more than 20 new features/enhancements, a lot of minor particulars have been tweaked and fine tuned to make this release a bigger milestone since PRADO 3.1.

Compatibility Information
Please see the upgrade instructions included in the release. In general, upgrading to PRADO 3.2.0 from 3.1.x or 3.0.x involves very little or no effort.
As usual we encourage you to report any problem so that we can make PRADO rock even better.

Time to party!

The PRADO Team
3  General / Announcements / We're back :) on: Apr. 19, 2012, 03:03:05 AM

our Hosting Provider moved our servers to a new datacenter. That went well, but the storage array didn't like being moved and decided to randomly kill harddrives. However, we're back and our desaster recovery plan worked quite well as we didnt loose a single file :-)

Greetings from Hamburg / Germany
- rojaro -
4  Prado v3.x / General PHP Topics / Re: [SOLVED] problems with $auth->login and 'ñ' on: Oct. 30, 2011, 12:09:50 AM
1. If you change it on the database, then you're just changing the default value that is used to create new tables.
2. This is basically the default value used to create databases
3. Thats the right way to update an existing table.

Greetings from Hamburg / Germany
- rojaro -
5  Prado v3.x / General PHP Topics / Re: problems with $auth->login and 'ñ' on: Oct. 29, 2011, 12:03:40 PM
Hi ClaCS,

"utf8_spanish_ci" is probably your problem. Thing is, when using any "*_ci" (case insensitive) collation, mysql does weird things to the chars i.e. treating "n" as the same as "ñ" although they're not. On the other hand, in some comparison operations they are not treated the same, which is why i always configure my databases as "utf8_bin". Other than that, your configuration looks alright.

However, also make sure that your html is actually valid utf8 by setting the meta charset tag and saving the templates in UNIX format. If not configured properly, the webbrowser will not send the user input from the text form fields as utf8 but (depending on the browser) will use ASCII or windows encoding instead, which will also break your encoding.

Btw. & @ctrlaltca, when setting the "Charset" property in the datbase config to 'utf8', the db abstraction layer will send "set names utf8" automatically, so there is no need to call mysql_query("SET NAMES 'utf8'", $connection);.

Greetings from Hamburg / Germany
- rojaro -
6  Prado v3.x / General PHP Topics / Re: problems with $auth->login and 'ñ' on: Oct. 28, 2011, 01:57:41 PM
Make sure your MySQL database collation is properly configured. Ideally you would be using "utf8_bin" (any other utf8_* collation should work as well but may have unwanted side effects).

Greetings from Hamburg / Germany
- rojaro -
7  Prado v3.x / General Discussion / Re: get .page content on: Oct. 18, 2011, 08:51:35 AM
Curl is an option, but you may also try something linke

$foo file_get_contents('http://localhost/path/to/page/');

Greetings from Hamburg / Germany
- rojaro -
8  Prado v3.x / General PHP Topics / Re: [SOLVED] TEmailAddressValidator ... bug? on: Oct. 14, 2011, 12:25:10 AM
The MX check in the email validator just does a DNS request to lookup the MX record for the domain part of the given email address. This does not gurantee that the email address itself exists at that server, but at least you'll know that you'll be able to deliver an email to the mailserver responsible for the domain (as long as the receiving mailserver is actually running and the mailserver will reject the email if the recipient is not known).

If i.e. you're providing a user registration or newsletter feature and you want to verify that the given email actually exists by sending an email containing a link with a token to activate the newly registered account, then you'll want to enable this check. It'll also help against typos in the domain name unless some typosquatter has registered that typo as domain.

If you want to have the user to type the email address twice by adding a second email address input field, then you'll want to disable the MX check for the second field.

Greetings from Hamburg / Germany
- rojaro -
9  Prado v3.x / General PHP Topics / Re: curiosity ... ActiveRecords, prado-cli.php and generation date on: Oct. 13, 2011, 02:12:52 AM
Your command line PHP interpreter probably uses a different configuration file than your webserver PHP module. Check your c:\wamp directory and its subfolders for other ini files.

Greetings from Hamburg / Germany
- rojaro -
10  Prado v3.x / General PHP Topics / Re: TEmailAddressValidator ... bug? on: Oct. 13, 2011, 02:09:19 AM
The email address validator not only checks whether the given email address is syntactically correct, but also checks whether a MX record was configured for the domain. You can use the "CheckMXRecord" property to disable this check.

Greetings from Hamburg / Germany
- rojaro -
11  Prado v3.x / Bug Reports / Re: Filelds non selectable with mouse on: Sep. 19, 2011, 07:51:47 AM
Check your CSS, you've got overlapping elements.

Greetings from Hamburg / Germany
- rojaro -
12  Prado v3.x / General Discussion / Re: I'm blocked on the forum on: Aug. 18, 2011, 02:37:29 PM
I got your PM and unflagged your posts, I just happend to be AFK Smiley

Greetings from Hamburg / Germany
- rojaro -
13  Prado v3.x / General Discussion / Re: Events inside a Custom TTemplateControl with Repeater containing buttons on: Aug. 18, 2011, 09:01:04 AM
Try 'SourceTemplateControl' instead of 'page'. That should do the trick Smiley

Greetings from Hamburg / Germany
- rojaro -
14  Prado v3.x / Bug Reports / Re: Bug report is not working on: Aug. 18, 2011, 08:57:56 AM

that was probably just a hickup at googlecode, because i've just tried it aswell and everything works just fine. Please try again.

Greetings from Hamburg / Germany
- rojaro -
15  Prado v3.x / Component Repository / Re: TExtDirectService v0.1 on: Aug. 02, 2011, 08:38:44 AM
One thing to watch out for: This implementation uses the ReflectionMethod "getDocComment" method, which will not work properly when using PHP with eAccelerator as that will strip the doc comments from the compiled byte code.
Pages: [1] 2 3 ... 49