Recent Posts

Pages: [1] 2 3 ... 10
1
VM uses the '_' character as a delimiter, when uploading images and generating thumbnails and URLs.

It used to be the case that, for SEO purposes, '-' was used to substitute a blank space and hence separate keywords.

Is it possible to use this as a filename delimiter for our image uploads from now on?

Thanks
2
Yes I completely agree.

The ability to update directly in Joomla is definitely "challenging".

Customers rarely read update notes and expect nothing to be impacted therefore update straight into live, it seems to be almost "promoted" by Joomla.

There is only this base "warning"

Code: [Select]
Notice
Before updating ensure that the update is compatible with your Joomla! installation.

Of course, the update IS compatible - It just might need careful consideration for all the extra plugins that are installed and configurations etc etc

Regarding the notes:-
Quote
you have no warning about template updates, module settings changes and all the problem you can have.

Yes I agree - that there should be some base paragraph that highlights the need for testing and careful consideration of module overrrides/template issues etc.

And possibly a - known - issues update
3
To show featured products turn their display on in your Joomla menu store item, on the subordinated category tab. Where they display is template dependant.
4
Ah, the problem here is that vm 3.4.0 is in the Joomla Updates and some users mean in this case that updating do not break the shop.
I know that you have to check and do backup, but some customer apply updates and complain after. I cannot prevent this.
if you read this https://virtuemart.net/news/490-virtuemart-3-4-prepare-for-the-future, you have no warning about template updates, module settings changes and all the problem you can have.
So shop owners mean that all these are only improvements and fixes without potential problems.
When i update Vm or Joomla i wait always 2 weeks minimum to do a list of potential problems and Virtuemart bug report get not added to the news about a release, even 1 month later, so all this bug report should be added to this news that you have not to do your own list of fixes and changes or add forum topic link
 with all know problem found after Eg the problem for the currency converter have 4 or 5 topics in this forum and in french Joomla and Vm forums, this should be added in news with a solution in the news list for eg.
But of course i like Virtuemart, else i had not spend so much time to do Vm2 MVC, multilanguage ... With max and Valerie for some years.
5
I just tried it. It doesn't change the ordering of the product (in category page).

btw... Default product sort order is set to "Product Name". We prefer alphabetical sorting as default, for normal products.
6
Administration & Configuration / Re: VM 3 Backend template (vs VM2)
« Last post by EvanGR on Today at 13:17:42 »
Here's the additional CSS for the Isis template...

I may have made changes to the php files as well, and some parts of this styling serves other purposes for our specific needs. Hope it helps.


Code: [Select]
.admin.com_virtuemart {
    background: #fafafa;
}

div#admin-content {
    /* background: #f8f8f8; */
    font-size: .9em;
    text-rendering: optimizeLegibility;
}


.admin.com_virtuemart .table th,
.admin.com_virtuemart .table td {
    padding: .2em .2em;
}

.admin.com_virtuemart .table  label {
font-weight: bold;
font-size: .9em;
}

.admin.com_virtuemart  .order_name {
    font-weight: bold;
    font-size: 1em;
}

.admin.com_virtuemart .order_email {
    color: #888;
}


.admin.com_virtuemart  .order_number > a {
    font-size: 1em;
    padding: .3em .2em;
    display: block;
    background: #eee;
    border: 1px solid #ddd;
text-decoration: none;
}
.admin.com_virtuemart  .order_number > a:hover {
border-color: #aaa;
background: #ddd;
color: #000;
}


.admin.com_virtuemart .shipment_method {
    font-size: .9em;
    line-height: 1.6em;
    color: #555;
}


.admin.com_virtuemart .payment_method {
font-weight: normal;
    padding: .2em .6em;
    border: 1px solid #ccc;
    display: inline-block;
    border-radius: 4px;
    background: #f0f0f0;
    font-size: .9em;
font-weight: bold;
line-height: 1.3em;
}

.admin.com_virtuemart .order_total {
    font-size: 1.3em;
    font-weight: bold;
    border: 1px solid #ccc;
    padding: .1em .4em;
    /* background: #eee; */
    text-align: right;
cursor: pointer;
}
.admin.com_virtuemart #final_price > div {
    font-size: 1.3em;
    font-weight: bold;
    background: #f0f0f0;
    border: 1px solid #aaa;
    /* margin: .1em; */
    line-height: 1.3em;
    padding: .2em .4em;
    cursor: pointer;
    display: block;
}

.admin.com_virtuemart .order_total:hover,
.admin.com_virtuemart #final_price > div:hover {
background: #fff;
}
.admin.com_virtuemart .order_total:active,
.admin.com_virtuemart #final_price > div:active {
background: #333;
color: #eee;
}


select, textarea, input[type="text"], input[type="password"], input[type="datetime"], input[type="datetime-local"], input[type="date"], input[type="month"], input[type="time"], input[type="week"], input[type="number"], input[type="email"], input[type="url"], input[type="search"], input[type="tel"], input[type="color"], .uneditable-input {
margin-bottom: .2em;
}

textarea#BT_customer_note_field {
    height: 8em;
    font-size: 1.2em;
    color: red;
}

7
OK, good to know. Hope we can catch this.

Jörgen @ Kreativ Fotografi
8
I am loading the admin products view using a modal window in another view (custom field) and facing the following issues:

1. Products do not show.
Seems like the the the products query is using the parent window's custom_id param:
Code: [Select]
WHERE ( ( (pf.`virtuemart_custom_id`="34" ) ) )
2. After a search for a product (when a custom_id exists in the parent window), the following sql error comes out:
Code: [Select]
Column 'product_sku' in where clause is ambiguous
Looking at your query in the sortSearchListQuery function, it turns out that:
a. Some fields are included more than once in the where clause, with different format.
Code: [Select]
$this->valid_search_fields;
0 = "product_name"
1 = "product_sku"
2 = "`l`.`slug`"
3 = "product_s_desc"
4 = "`l`.`metadesc`"
6 = "`p`.product_sku"
8 = "product_desc"
9 = "category_name"
10 = "category_description"
11 = "mf_name"

b. Some of the fields do not contain the table name or the alias, becoming ambiguous.
9
Thanks again.

How can I tweak this code so that I just generate and use the thumbnail filename, but not display it? (VM creates its own img element)

I like to construct my own custom <img /> elements, with additional lazy-loading code and utilizing the <picture> element for image sets.
10
Quote
Ah, i contributed more then 1500 hours to VM,  so i think i can ask a question to know if Vm 3.4 was fully tested or not.

I am unsure as to why you think you could not ask - of course anyone (regardless of hours contributed) can ask - The term "fully tested" is open to debate and interpretation.

The extent to which the release was fully tested is based on the availability of technical environments and specific Joomla and VM configurations.  As we are all aware, these are myriad - and it is in no way practicable or possible to replicate all of these for testing purposes, as a result, certain aspects may remain "untested" in any one release.
However, the response to any issues post release is swift and should satisfy the vast majority of business users - (Assuming that they have taken the basic industry approach, that is to deploy and test in their own testing systems prior to deploying in live.)

Quote
You complained for some years about code changes, but each new release we have to check what have changed to not get complains for own customers.

Because you have customers using a third party solution, you incur additional effort in reviewing the changes to understand potential impact on your customers.
They are your customers, you are using third party freely supplied solutions and yet you appear to expect that you should incur no additional impact when code changes - this seems somewhat aspirational.

Regarding the legitimacy of your question, all are legitimate but, I would have anticipated that someone with customers using the software would have made use of the release notes.  In reading such notes, it would be clear that if this were a "Beta release", it would state "this is beta".

http://virtuemart.net/news/490-virtuemart-3-4-prepare-for-the-future

Consequently the answer to your question 
Quote
Hum, is 3.4 a beta or not ?

3.4 is Not a beta release.
Pages: [1] 2 3 ... 10