v1.0.8.0 Questions / Comments / Concerns

[Pierre_P]

Language file administrators_WG.php missing?

[ecartz]

Language file administrators_WG.php missing?

There is no core file named administrators_WG.php

Add-on?

[Pierre_P]

addon it was

[raiwa]

If I well remember, the name of the main file doesn’t match the names of the language files. Change to be all lower case.

[Nigel]

The Buy Button and Objects & Attribute Content Modules are available for product_info but are also present as standard.
The pic shows two instances of each.

prod_info_x2.png

[zipurman]

That means that you have both the buy buttons turned on as a Product Info Module as well as a PI Module.

One is in the Admin -Modules - Content - (labeled as product_info) (Options & Attributes / Buy Button)

On is in the Admin - Product Info - (Options & Attributes / Buy Button)

[Nigel]

That means that you have both the buy buttons turned on as a Product Info Module as well as a PI Module.

One is in the Admin -Modules - Content - (labeled as product_info) (Options & Attributes / Buy Button)

On is in the Admin - Product Info - (Options & Attributes / Buy Button)

So not really as standard but duplicate from another option I'd already used.
The same with "model" too.

I saw them in the Content option and wondered if they were the same and tested it to confirm.
Do we need this option available from two different locations ?

Thanks for the reply.

[zipurman]

The PI or Product Info modules give more control over placement. The PI or π module needs to be installed into Content Modules, and then you can go to Admin - Product Info to configure them. The other duplicate modules can be disabled in Admin - Content - product_info items as they pre-date PI.

[ecartz]

Do we need this option available from two different locations ?

I don't know. Some questions that would need answering to determine this:

1. Can you match the display of the content modules with the PI modules in all circumstances? I'm inclined to believe that you can't, but I do not know that for sure.
2. How many store owners use the content module version?
3. How many store owners use the PI version?
4. Why? (Possibly #1 or possibly something else.)

These aren't technical questions but business questions. If you can demonstrate that having the two options does not add flexibility that store owners value, we could remove the content modules. But until someone goes through the work to do that, this isn't something that we are likely to prioritize.

1. It's possible that having both is necessary.
2. We have to support some content modules regardless, as they are used on other pages that don't have PI modules.
3. PI modules are more powerful in layout terms than content modules. So we aren't going to remove them.
4. If you don't want to use one or the other, you don't have to do so. Neither is imposed upon you.

Overall, we will tend to focus on increasing flexibility rather than reducing it. I don't know that keeping the product_info content modules is necessary. But I don't know that it's not. As such, it is easier to let individual store owners make that determination.

If we did remove those content modules, the goal would likely be to reduce our maintenance overhead. But even there, I don't see these as the leading edge. I would be more likely to remove Who's Online and Open Search as two things that we aren't really using that could be add-ons instead.

[WP Horlogebanden]

Hello,
I just updated from 1.0.7.15 to 1.0.8.0 (via 1.0.7.16). I noticed some changes, which I may have overlooked in the past. I am messing with core code, so: my fault. I do have an operational site despite my messing with the core. The comparison between 1.0.7.16 (via 1.0.7.18 to 1.0.8.0) shows 1 more file than update.zip.

To be completely sure I am back on track with all previous changes, I downloaded from phoenixcart.org the new release. I noticed that install\phoenix.sql is incorrect as Cote D'Ivore messes up de sql. In the new github, I see this has already been solved. It would be nice however for any new users that installation does not fail, due to this error. Please update the installaton a.s.a.p. (which is "as soon as possible for you", off course).