Yup - you are right- I've never tried POG update- I was always afraid
(if it ain't broke, don't fix it).
Also- I think I have run into a flaw in my "process". When I update an
object, I place the zip file at the root of my project, then unzip
"here" which overwrites that object in the objects folder, as well as
the configuration.php file. I always open the configuration.php file
in an editor, expand the zip, revisit the editor and I do not reload
configuration.php. I then save as to write my configuration.php back
out. This is to save me the hassle of having to modify the file with
my server creds and plugin path every time I regen an object.
It appears to have bitten me this time because I end up throwing away
other changes to the configruation.php file that POG puts in there,
like when there is a version update.
So- this is likely the source of my initial error at least. However,
I'll wait for you to do whatever you are planning on your end.
It would be really cool if there was an ini file or something that I
could place my database creds and plugin path info into, and then
setup could read that and adjust the configuration file when it does
the pog me up stage. Or something like that.
I see that my objects are currently on POG version 3.0d.
Thanks for the great work, Joel and the quick reply.
On Jul 9, 1:09 pm, Joel <
joel...@gmail.com> wrote:
> Hi,
>
> I've looked into your issue. Seems that there is a problem on our end.
> The problem was probably introduced this week, when our servers were
> upgraded to PHP 5...
>
> I'll first answer your question "Now, I see reference to POG 3.How can
> I tell what version I'm currently using?". The version is stored in
> the phpdoc of your object @version
>
> The problem is two fold:
>
> problem 1
> - you can't update your objects using POG update because the soap
> server that is in your config file is now invalid. You need to change
> it tohttp://
www.phpobjectgenerator.com/services/pog.wsdl