Hi Fabien,
@rename does not work, because it issues a Warning, which is the root cause
for people on this thread.
Fabian
On Thu, Apr 2, 2009 at 8:49 AM, Fabien Potencier <
fabien.potenc...@symfony-project.com> wrote:
>
> I have updated the patch for all versions of symfony because contrary to
>
I have updated the patch for all versions of symfony because contrary to
the rename() function, the copy() function works as expected on Windows.
Moreover, as of PHP 5.2.6, the rename() function works. So, I have
applied the same trick that Agavi did to fix the same race condition
problem (htt
Shame on PHP indeed - I just read the full thread on that bug report,
are the developers always that rude to their bug reporters?
Thanks for the fix Fabian. Do you have any idea when you will release
this as a live update via PEAR? I'd really like to gain the fixes
available in 1.2.5 but at pre
Hi,
I added the file_exists.
http://trac.symfony-project.org/changeset/16847
Actually the root of all evil is rename() because it doesn't work on
windows.
PHP Devs ignore that:
http://bugs.php.net/bug.php?id=44805 claims it is fixed, but it is not
http://bugs.php.net/bug.php?id=41985 is full of in
Ah, yes, I do use sfErrorHandlerPlugin. However, would it really be a
big performance hit to check that the file exists before calling an
unlink on it rather than unlinking a non-existant file and just
telling PHP to ignore errors (which doesn't seem particularly good
practice to me).
On Apr 1,
Ok, this is actually caused by sfErrorHandlerPlugin, if i move it out
of my plugins folder, the page loads fine now. Looks like it may be
sfErrorHandlerPlugin being a bit over zealous in reporting errors if
its catching @ suppressed errors...
-J
On Tue, Mar 31, 2009 at 7:44 AM, Fabian Lange
wr
Hi,
could be error reporting.
The four digit file exists, because it is the new file that shall replace
the old one. Due to the way it is implemented in PHP we need to remove the
file .yml before we move the . to its place. However the unlinking fails
which sucks...
I am open for ideas and will
Hi, I get this exact same problem - an sfLegacyException because it
tries to unlink a cached view.yml file. What is odd is that the
view.yml file in question does kind of exist, except that it ends with
xxx_view.yml. (with the final four digits being a four digit
number). This only happens in
Hi,
is it this line?
http://trac.symfony-project.org/browser/branches/1.2/lib/config/sfConfigCache.class.php#L352
I am a bit confused that you receive an error, because the "warning"
should be suppressed by the preceding @ and the unlink just shouldn't
do anything.
Clues anyone?
Fabian
On M
