My company is looking for someone (consultant) to install Midgard for us on a 
disc that we can send.

If you are interested or know of anyone please have them contact me.
[EMAIL PROTECTED]
or [EMAIL PROTECTED]


Samar Elatta
Technical Consultant
Certified ScrumMaster

(402) 699-0427


Securities America, Inc., a Registered Broker/Dealer, Member FINRA/SIPC.  
Advisory services offered through Securities America Advisors, Inc., An SEC 
Registered Investment Advisory Firm.
The text of this communication is confidential, and use by any person who is 
not the intended recipient is prohibited.  Any person who receives this 
communication in error is requested to immediately destroy the text of this 
communication without copying or further dissemination.  Your cooperation is 
appreciated.

________________________________

From: [EMAIL PROTECTED] on behalf of [EMAIL PROTECTED]
Sent: Sat 7/19/2008 5:00 AM
To: [email protected]
Subject: --SPAM-- user Digest, Vol 14, Issue 6



Send user mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.midgard-project.org/mailman/listinfo/user
or, via email, send a message with subject or body 'help' to
        [EMAIL PROTECTED]

You can reach the person managing the list at
        [EMAIL PROTECTED]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of user digest..."


Today's Topics:

   1. Re: Segfault in DM2 edit forms (Andreas Flack)
   2. Re: Segfault in DM2 edit forms (Piotr Pokora)
   3. New Midgard 1.9 packages  (Piotr Pokora)
   4. Re: Segfault in DM2 edit forms (Andreas Flack)
   5. Re: Segfault in DM2 edit forms (Piotr Pokora)
   6. Re: Usability of midgard-project.org (Andreas Flack)


----------------------------------------------------------------------

Message: 1
Date: Fri, 18 Jul 2008 12:54:34 +0200
From: Andreas Flack <[EMAIL PROTECTED]>
Subject: Re: [midgard-user] Segfault in DM2 edit forms
To: Midgard user list <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=UTF-8; format=flowed

Hi!

I tried setting all int and float fields to NOT NULL default 0, but that
doesn't mak a difference. Also, I have another MgdSchema type where
floats are nullable which is working fine, so my problem doesn't seem to
be related to that.


Bye,

Andreas

Marcin SoÅ'tysiak schrieb:
>>>> On my Kubuntu 8.04 installation, I noticed segfaults in some DM2 forms.
>>>> Strangely enough, they only occur for some of my self-written MgdSchema
>>>> objects (others and built-in ones are working fine), but I can't quite
>>>> make out what the error could be. On a different machine (with openSUSE
>>>> 9.2), they work fine, so I'm a bit lost.
>>>>
>>>> The backtrace looks like this:
>>>>
>>>> Program received signal SIGSEGV, Segmentation fault.
>>>> [Switching to Thread 0xb77f2700 (LWP 8418)]
>>>> 0xb6c79a13 in set_gobject_property_from_zobject (obj_ptr=0x9b65d2c,
>>>> gobject=0x9a62540)
>>>>     at
>>>> /home/sonic/downloads/software/Midgard_AllinOne-1.8.8/midgard-php4-1.8.8/midgard.c:627
>>>>
>>>>
>>>> 627           if (propname && (*property)->refcount) {
>>>
>>> Did you test direct update/create/get on this objects?
>>
>> I tried update() with the DBA object and it produces the same
>> backtrace. update() on the Midgard object is working, however.
>
> How about nulls?
>
> http://marcin.soltysiak.com/view/null-values-issue.html
>
> Solt
> _______________________________________________
> user mailing list
> [email protected]
> http://lists.midgard-project.org/mailman/listinfo/user



------------------------------

Message: 2
Date: Fri, 18 Jul 2008 13:17:41 +0200
From: Piotr Pokora <[EMAIL PROTECTED]>
Subject: Re: [midgard-user] Segfault in DM2 edit forms
To: Midgard user list <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=UTF-8

Andreas Flack writes:
> Hi!
>
> I tried setting all int and float fields to NOT NULL default 0, but that
> doesn't mak a difference. Also, I have another MgdSchema type where
> floats are nullable which is working fine, so my problem doesn't seem to
> be related to that.

NULLs bug is already fixed in 1.8.8.
I have no real solution for Your problem atm , but it segfaults when we
list PHP objects' properties.
Try to print_r DBA object to see if all properties are correctly assigned.

Piotras


------------------------------

Message: 3
Date: Fri, 18 Jul 2008 13:32:52 +0200
From: Piotr Pokora <[EMAIL PROTECTED]>
Subject: [midgard-user] New Midgard 1.9 packages
To: Midgard user list <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=UTF-8

Hi!

It's not yet stable release, but we slowly prepare for beta :)
If you want to experiment with newest Midgard snapshots, read my blog
about how to install it easily.
http://blogs.nemein.com/people/piotras/view/1216379189.html

No, it's not recommended for production usage, but it's enough stable to
install it and use.
There are no database changes required, so it's enough to update only
Midgard packages itself.

Keep in mind that Midgard 1.9 requires MidCOM 2.9, which is
automatically installed with new datagard.
Important! It can not be used in parallel with Midgard 1.8/Midcom2.8 series.

Piotras


------------------------------

Message: 4
Date: Fri, 18 Jul 2008 13:36:16 +0200
From: Andreas Flack <[EMAIL PROTECTED]>
Subject: Re: [midgard-user] Segfault in DM2 edit forms
To: Midgard user list <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=UTF-8; format=flowed

Piotr Pokora schrieb:
> Andreas Flack writes:
>> Hi!
>>
>> I tried setting all int and float fields to NOT NULL default 0, but that
>> doesn't mak a difference. Also, I have another MgdSchema type where
>> floats are nullable which is working fine, so my problem doesn't seem to
>> be related to that.
>
> NULLs bug is already fixed in 1.8.8.
> I have no real solution for Your problem atm , but it segfaults when we
> list PHP objects' properties.
> Try to print_r DBA object to see if all properties are correctly assigned.

They all looked fine. The only thing I found strange is that there was a
property called "action" with an empty value. I don't have a property
with that name, so it must get added automatically somewhere.

By playing around a little, I now found the problem: One of the DBA
classes contained a private var. When I changed this to public, the
segfaults for both DBA classes went away (the other class is the child
of the one with the private var). Is that a bug or is it generally not
allowed to add private vars to a DBA class?


Bye,

Andreas

>
> Piotras
> _______________________________________________
> user mailing list
> [email protected]
> http://lists.midgard-project.org/mailman/listinfo/user



------------------------------

Message: 5
Date: Fri, 18 Jul 2008 14:03:06 +0200
From: Piotr Pokora <[EMAIL PROTECTED]>
Subject: Re: [midgard-user] Segfault in DM2 edit forms
To: Midgard user list <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=UTF-8

Andreas Flack writes:

Hi!

>> Try to print_r DBA object to see if all properties are correctly
>> assigned.
>
> They all looked fine. The only thing I found strange is that there was a
> property called "action" with an empty value. I don't have a property
> with that name, so it must get added automatically somewhere.

Yes, it's base midgard_object property. As well as guid and metadata for
example.

> By playing around a little, I now found the problem: One of the DBA
> classes contained a private var. When I changed this to public, the
> segfaults for both DBA classes went away (the other class is the child
> of the one with the private var). Is that a bug or is it generally not
> allowed to add private vars to a DBA class?

MidCOM 2.8 is not pure PHP5 framework. It was only adopted to run with PHP5.
The same midgard-php bindings. That's why I didn't renamed it to
midgard-php5.

I doubt it can be fixed in 1-8 branch. At least it should work perfectly
with upcoming 1.9 release.
Midgard-php5 there, is pure language bindings.

Piotras



------------------------------

Message: 6
Date: Sat, 19 Jul 2008 01:14:05 +0200
From: Andreas Flack <[EMAIL PROTECTED]>
Subject: Re: [midgard-user] Usability of midgard-project.org
To: Midgard user list <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="utf-8"

Hi!

I know it's a bit late to respond now, but I just stumbled across a
company called startssl, which actualy offers (some) SSL certificates
for free:

http://www.startssl.com/?app=1

The good thing is that their root certificate is included in FF3 by
default, so the security warning mentioned below won't appear. So unless
the currently-used self-signed certificate has some enefits I'm not
aware of, I would propose to switch to a startssl one, since the FF3
security warnings really make m-p.org look bad.


Bye,

Andreas

Edward Z. Yang schrieb:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello all,
>
> I recently hopped over here in order to answer a few questions regarding
> a library I developed that Midgard uses. In the process, I got myself a
> user account. Along the way, I found a few gotchas that were really
> annoying:
>
> 1. The SSL certificate is signed by an unverified certificate authority
> and errors in most browsers. With Midgard's strong commercial presence,
> wouldn't it make sense for The Midgard Project to invest in, say, a
> VeriSign cert? (any CA that ships with the majority of browsers works)
>
> 2. The very-essential grey toolbar that offers many essential functions
> (in my case, changing passwords), does not appear unless JavaScript is
> enabled. I use NoScript, but have no problem turning on JavaScript for
> websites that genuinely need it. Midgard gave me *no* indication that I
> was missing functionality because JavaScript was turned off. <noscript>
> would be helpful in this context.
>
> 3. Midgard only supports logins via https. However, static page elements
> are occasionally linked to using http, which causes browsers to throw
> errors. This problem appears to be intermittent.
>
> 4. There is no visual indication if the grey toolbar's buttons (Page /
> Folder / Website) are disabled or have no entries. Before I realized
> that this toolbar was per page (non-obvious), I was scratching my head
> trying to figure out why Page and Folder didn't seem to work. I would
> suggest greying them out or simply removing them completely.
>
> 5. The first instinct for someone seeking to make a post or answer a
> question in the Discussion Forums is to use the facilities listed there.
> However, the response gets mirrored to the mailing list, where it gets
> caught by the moderator and languishes there. It should be made clear
> that the mailing list is the preferred method of communication. If
> you're interested in fixing this bug, user registration should also
> register users for the mailing lists, but should keep mail delivery off.
>
> 6. Midgard's forgotten password messages are cryptic. The one I recieved
> looked like this:
>
> From: [EMAIL PROTECTED]
> Subject: Your password has been reset.
>
> Your password has been reset to:
>
> zgnjtbxt
>
> Why is this from my email address, and not [EMAIL PROTECTED]
> (At the very least, the site name should be mentioned in the subject)
> I'm also a strong proponent of the "Give user a token to change their
> password" rather than the random password generation setup. This might
> even have the capacity to annoy users, if the old password is not kept
> (an arbitrary person could force the user to change their password many
> times. Haven't tested, of course).
>
> 7. It's extremely difficult an non-intuitive to find the member info
> page (Community > Registration). I recommend linkifying the logged in
> user name (found in the top right corner) to point to this page.
>
> 8. Midgard really should be verifying email addresses on registration.
>
> And that's it for now. Thanks for reading! I hope to be working with you
> guys in the future to improve Midgard's integration with HTML Purifier.
>
> Cheers,
> Edward
>
> - --
>  Edward Z. Yang                        GnuPG: 0x869C48DA
>  HTML Purifier <http://htmlpurifier.org <http://htmlpurifier.org/> > Anti-XSS 
> Filter
>  [[ 3FA8 E9A9 7385 B691 A6FC B3CB A933 BE7D 869C 48DA ]]
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org 
> <http://enigmail.mozdev.org/>
>
> iD8DBQFINIFSqTO+fYacSNoRAqgXAJ9FhrGHG1q8ILS8ei9MDNBDC5N4PwCbB0ET
> Nl0MDB9Nr+l6glVsJISUsTc=
> =Mtd0
> -----END PGP SIGNATURE-----
> _______________________________________________
> user mailing list
> [email protected]
> http://lists.midgard-project.org/mailman/listinfo/user

-------------- next part --------------
A non-text attachment was scrubbed...
Name: flack.vcf
Type: text/x-vcard
Size: 301 bytes
Desc: not available
Url : 
http://lists.midgard-project.org/pipermail/user/attachments/20080719/4b3b94f2/flack-0001.vcf

------------------------------

_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user


End of user Digest, Vol 14, Issue 6
***********************************








The text of this communication is confidential, and use by any person who is 
not the intended recipient is prohibited. Any person who receives this 
communication in error is requested to immediately destroy the text of this 
communication without copying or further dissemination. Your cooperation is 
appreciated.
_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user

Reply via email to