Issue installing in org with Managed Packaging namespace about milestones-pm

[ReidCarlberg]

OK, looks like its running into a search error when attempting to test the search function on the controller.
Questions:
are you installing using the unmanaged package or by pushing code?
are you installing fresh or over an existing version?
is Milestones PM to be a part of this managed package?

[plmcgrn]

Using the package installer via AppExchange
Installing fresh (you can't install over unmanaged packages can you?)
It is not to be part of that package

/Paul

On Tue, Oct 4, 2011 at 11:04 AM, ReidCarlberg <
[email protected]>wrote:

OK, looks like its running into a search error when attempting to test the
search function on the controller.
Questions:
are you installing using the unmanaged package or by pushing code?
are you installing fresh or over an existing version?
is Milestones PM to be a part of this managed package?

Reply to this email directly or view it on GitHub:

#31 (comment)

[ReidCarlberg]

You can ignore apex errors. I'll still work on this, just don't have a solution for it yet. Can't reproduce it.

[plmcgrn]

That'd work for sandbox, but not prod. Unmanaged packages still run tests
when you push Apex to the environment, so this would be the last deployment
we'd be able to do. Right?

/Paul

On Wed, Oct 5, 2011 at 12:48 PM, ReidCarlberg <
[email protected]>wrote:

You can ignore apex errors. I'll still work on this, just don't have a
solution for it yet. Can't reproduce it.

Reply to this email directly or view it on GitHub:

#31 (comment)

[ReidCarlberg]

Looks like these are related to the way I was reference field names. I have a change coming up for this -- sometime in the next few days.

[ReidCarlberg]

Paul -- LMK if we need to reopen this, otherwise I'll assume closed.