[MOD] - VirtualQMod "vQmod" Virtual File Modification System

its 755 or 777... thats all it can be. If one doesn't work, try the other.

OK, I manually added the changes in the 2 index.php files, re-uploaded the vqmod files and it automatically set the rights on the folders to 0755.
I now can enter the storefront and admin without errors.

How can I easily check if it works, I see nothing appear in the vqmod cache folder.

OK, it works.

No clue why it did not work yesterday.

I'm *occasionally* (maybe 1 out of 10 reloads) getting the following error message:

VQMOD: Could not delete vqmod/vqmod.log.
Verify path has read/write access
Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/account/public_html/vqmod/vqmod.php:224) in /home/acciybt/public_html/system/library/session.php on line 11

--------

Any suggestions?

tjonnyc wrote:I'm *occasionally* (maybe 1 out of 10 reloads) getting the following error message:

VQMOD: Could not delete vqmod/vqmod.log.
Verify path has read/write access
Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/account/public_html/vqmod/vqmod.php:224) in /home/acciybt/public_html/system/library/session.php on line 11

--------

Any suggestions?

Are you using vQmod v1.2.3?

Using 1.0.9.

tjonnyc wrote:Using 1.0.9.

Well then guess what my next comment will be.

uksitebuilder wrote:Not sure if this is an OC bug or due to having vQmod installed but I think it is vQmod

On a demo store with demo products installed, edit the Apple Cinema 30" product and click save.

if public $useCache = FALSE in vqmod.php then the following error is displayed:

Code: Select all

Notice: Undefined index: option_value_id in/htdocs/site/admin/model/catalog/product.php on line 169Warning: Cannot modify header information - headers already sent by (output started at/htdocs/site/admin/index.php:79) in/htdocs/site/vqmod/vqcache/vq-system_engine_controller.php on line 28Warning: Cannot modify header information - headers already sent by (output started at/htdocs/site/admin/index.php:79) in/htdocs/site/vqmod/vqcache/vq-system_engine_controller.php on line 29

setting $useCache = TRUE in vqmod.php then the error goes away


In addition, I think the default for $useCache is FALSE in vqmod.php

this means that the cache files are rewritten each time the page loads that has been modded. I have noticed a slight performance hit with this.

I had this exact same problem after installing vQMod.

According to Qphoria i really needed to increase Upload, Post and Timeout parameters.

I asked my server Customer Service to increase these parameters and the problem solved.

Looks like the following XML file (extracted from a bigger XML file of mine from one of my projects) causes the changes to applied twice instead of just once to the file (the setting.tpl in this example) to be modified. Is this a bug in VQmod 1.2.3?

JNeuhoff wrote:Looks like the following XML file (extracted from a bigger XML file of mine from one of my projects) causes the changes to applied twice instead of just once to the file (the setting.tpl in this example) to be modified. Is this a bug in VQmod 1.2.3?

Code: Select all

<modification>
	<id>Opencart core file modifications for the setting.tpl</id>
	<version>1.5.1.1</version>
	<vqmver>1.2.3</vqmver>
	<author>mhccorp.com</author>
	
	<file name="admin/view/template/setting/setting.tpl">
		<operation>
			<search position="after" offset="2"><![CDATA[<span class="error"><?php echo $error_image_additional; ?></span>]]></search>
			<add><![CDATA[
            <tr>
              <td><span class="required">*</span> <?php echo $entry_image_popup_additional; ?></td>
              <td><input type="text" name="config_image_popup_additional_width" value="<?php echo $config_image_popup_additional_width; ?>" size="3" />
                x
                <input type="text" name="config_image_popup_additional_height" value="<?php echo $config_image_popup_additional_height; ?>" size="3" />
                <?php if ($error_image_popup_additional) { ?>
                <span class="error"><?php echo $error_image_popup_additional; ?></span>
                <?php } ?></td>
            </tr>
			]]></add>
		</operation>
	</file>
	
	<file name="admin/view/template/setting/setting.tpl">
		<operation>
			<search position="after" offset="1"><![CDATA[<td><textarea name="config_meta_description"]]></search>
			<add><![CDATA[
            <tr>
              <td><?php echo $entry_meta_keywords; ?> setting.tpl</td>
              <td><textarea name="config_meta_keywords" cols="40" rows="5"><?php echo $config_meta_keywords; ?></textarea></td>
            </tr>
			]]></add>
		</operation>
	</file>
</modification>

you should put all changes for a given file as seperate operations under one file tag. It sometimes does strange things when you have multiple file tags with the same file inside one xml.

you should put all changes for a given file as seperate operations under one file tag. It sometimes does strange things when you have multiple file tags with the same file inside one xml.

I noticed that, after a some trial and error sessions

However, I still think that this should be addressed, quite often I group my different <file>....</file> with their <operation>....</operation> elements according to the wanted feature. E.g. one feature is adding support for meta_keywords for the home page, another one is adding support for additional popup image size, or another one for adding support for Google AdWords Conversion tracking, etc., and each time it adds configuration details into the setting.php and setting.tpl. For the time being I have bypassed this issue by creating separate XML files for each new feature.

Yes it is a known issue with the 1.x version that using multiple file tags with the same file causes this.
I believe the 2.x version resolves this. If you could try it with JayG's updated version (PM'd to you) and see if that resolves it... I will work with him to get that released.

Yup 2.0 does solve this. JNeuhoff already had a link to the repo

Do I need to alter the mods that are using vqmod if I start using the 2.0?

Nope, 2.0 is based on 1.x but will be object based, making it easier to modify/read through

Thanks jay
Waiting for the 2.0 release

Yea I think it is time to push 2.0 out.
Tho I personally prefer the smaller logging format from 1.2.3
The logs in 2.0 are a bit bloated

But I'll let you guys be judge

Qphoria wrote:Yea I think it is time to push 2.0 out.
Tho I personally prefer the smaller logging format from 1.2.3
The logs in 2.0 are a bit bloated

But I'll let you guys be judge

There is still a bug in VQmod 2.0 (see my PM) which needs fixing.

I am about to release some mods/extensions i wondered where the repository is for vQmod 2.0?
Greetings
boriscm

Hi Boriscm

It's not available to the public yet. I will update once it is. You can just create and test your vQmod with 1.2.3, if it works with that it should work with 2.0, no features will be removed

First, where do I get vQmod 2.0?

Secondly, I'm using 1.2.3 now and I'm wondering can vQmod be used to modify db quires? I am trying to modify the following db query
to be
and it's telling me that the search failed (aborted). I'm copying and pasting this db query directly from the core file (admin/model/catalog/product.php) into the vQmod so i'm not sure why it's saying it can't find the code.

Any ideas? Here's what that section of the vQmod looks like.