Closed GoogleCodeExporter closed 9 years ago
What was the problem with packaging it yesterday?
Anything new we need to know?
So it's FixedQty and that other ContentMigration one.
Has to be tested before releasing to magentoconnect.
Original comment by zetapri...@gmail.com
on 17 Feb 2011 at 8:28
I package extensions by hand. And it turned out that new mage script simply
doesn't work. I found another way for me to package exts.
Petar, should continue packaging as he did it before. He just need to repackage
all his exts. in M 1.5
Why is it Stream-FixedQty? We need to re-package all our extension.
Original comment by Anatoly....@gmail.com
on 17 Feb 2011 at 8:43
Sorry, misunderstanding.
Anatoly, maybe you do them all yourself this time?
Original comment by zetapri...@gmail.com
on 17 Feb 2011 at 9:10
Issue 464 has been merged into this issue.
Original comment by zetapri...@gmail.com
on 17 Feb 2011 at 9:12
Well, then I need M. packager settings from Petar.
Original comment by Anatoly....@gmail.com
on 17 Feb 2011 at 9:32
sure, which ones are they? The ones with package name in pear folder?
By the way where can I get info about packaging by hand?
Original comment by jamb...@gmail.com
on 17 Feb 2011 at 10:39
Attachments:
Are we definitely moving on 1.5 development?
To which versions should we aim to support?
Original comment by jamb...@gmail.com
on 17 Feb 2011 at 10:41
We have no choice.
At the same time we can't just drop 1.4 support.
There are bug fixes that our existing customers depend on.
They will migrate, but some time later.
Original comment by zetapri...@gmail.com
on 17 Feb 2011 at 10:52
By the way, I have tried to install attachments and fixed qtys on 1.5.0.1 using
version 2 of magento connect and it worked perfectly. So repackaging is not
extra urgent thing.
Original comment by jamb...@gmail.com
on 17 Feb 2011 at 11:14
Hm, it doesn't work for me. Strange
Original comment by Anatoly....@gmail.com
on 18 Feb 2011 at 3:54
I just went on magento site, picked our extension (attachments, fixed prices)
asked for code, and choose version 2 of magento connect. That is all, and it
installed.
Original comment by jamb...@gmail.com
on 18 Feb 2011 at 8:00
Yeah, I did same. I'm not lucky this time.
Original comment by Anatoly....@gmail.com
on 18 Feb 2011 at 9:07
[deleted comment]
Petar, could you please try to install access control, for example?
Original comment by Anatoly....@gmail.com
on 18 Feb 2011 at 7:02
Sure no problem.
Entire process with screen shots.
1. Grab version 2 extension key
2. Go to magento connect manager and paste key.
3. MC says ready to install, click preceed
4. Seems more or less the same as before.
5. Extension in place.
Original comment by jamb...@gmail.com
on 18 Feb 2011 at 7:21
Attachments:
One thing I just noticed. Today I wasn't able to see any categories on home
page or access any category by direct link. After trying all things I can think
of, I remembered that last thing I did to the site is install access control.
I checked its default settings and it was enabled and my default to categories
by customer groups' was set no NONE, so this prevented any access to categories.
Is this supposed to be like this by default?
If yes, then I think that admin note should be put on top of admin page as a
reminder to change the setting to something more useful.
Original comment by jamb...@gmail.com
on 21 Feb 2011 at 9:26
@16 - worth posting an issue about it
Original comment by zetapri...@gmail.com
on 21 Feb 2011 at 10:19
Original comment by ad...@zetaprints.com
on 21 Apr 2011 at 12:33
where is it at ?
we released it for 1.5
is there anything outstanding from this issue?
Original comment by ad...@zetaprints.com
on 21 Apr 2011 at 12:36
I think all our exceptions are just fine for 1.5, anyway Magento recommends to
upload older type of packages if we want certain extensions to be available for
1.4.2 and less.
So for this issue - FQ is repacked for 1.5 but it doesn't need to be.
Original comment by jamb...@gmail.com
on 21 Apr 2011 at 5:56
We'll target 1.5 unless someone asks for 1.4.2
Original comment by ad...@zetaprints.com
on 21 Apr 2011 at 12:42
Original issue reported on code.google.com by
Anatoly....@gmail.com
on 17 Feb 2011 at 7:52