Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums

(Advanced Search)

Forum Statistics
» Members: 38
» Latest member: zxlbxj1
» Forum threads: 59
» Forum posts: 225

Full Statistics

Online Users
There are currently 11 online users.
» 0 Member(s) | 11 Guest(s)

Latest Threads
Icons below products
Forum: Bug Reports
Last Post: davidb
11-08-2018, 01:28 PM
» Replies: 1
» Views: 134
Discover NivoCart!
Forum: General Discussion
Last Post: villagedefrance
10-31-2018, 05:09 PM
» Replies: 0
» Views: 45
OpenCart v3.0 impressions
Forum: General Discussion
Last Post: villagedefrance
10-31-2018, 05:01 PM
» Replies: 19
» Views: 4,092
Authorize.net AIM and SIM...
Forum: Extensions and Modules
Last Post: villagedefrance
10-31-2018, 04:39 PM
» Replies: 1
» Views: 93
New Marketplace features
Forum: General Discussion
Last Post: gob33
10-17-2018, 12:11 AM
» Replies: 12
» Views: 797
Commercial Template Avail...
Forum: Custom Templates
Last Post: redjaffa
09-17-2018, 02:14 PM
» Replies: 0
» Views: 104
Remove product from Featu...
Forum: Bug Reports
Last Post: Sp1ke
09-14-2018, 03:18 AM
» Replies: 0
» Views: 131
New Demo data products
Forum: General Discussion
Last Post: gob33
08-23-2018, 09:44 PM
» Replies: 3
» Views: 262
Overclocked going forward...
Forum: General Discussion
Last Post: villagedefrance
07-30-2018, 03:05 PM
» Replies: 9
» Views: 655
OpenBay Pro Poll
Forum: General Discussion
Last Post: gob33
07-25-2018, 10:20 PM
» Replies: 5
» Views: 1,150

 
Information Coding Standards
Posted by: villagedefrance - 07-24-2017, 12:04 PM - Forum: F.A.Q and Tutorials - No Replies

OpenCart Overclocked Edition uses strict coding rules, as follow:

* File types & encoding
* PHP tags
* Indentation
* Spacing
* Whitespace
* New lines
* File naming
* Class & method naming
* Helper naming
* PHP variable naming
* User defined constants
* PHP constants
* HTML / CSS rules

File types & encoding
All PHP files with the exception of view/template files have the extension .php

All view/template files have the extension .tpl

***
PHP Tags
Short PHP opening tags and ASP tags are not supported. The characters should be lowercase.

<?php


All PHP files must include a closing tag for versions before 1.8.1 (and 2.0.0). PHP files in and after 1.8.1 will no longer have a closing tag, but an empty line instead.

?>


***
Indentation
PHP files must be indented using the TAB character. 4 space tabs are not supported.

HTML in template files (.tpl) must be indented using 2 spaces, not 4 spaces or TABS. JavaScript must be indented using the TAB character.

***
Spacing
IF, WHILE, FOR etc should have a space before and after the brackets.

Correct:

if () {

Incorrect:

if(){


ELSE etc should have a space after and before the curly braces

Correct:
} else {

Incorrect:
}else{

Type casting does NOT have a space before the variable

Correct:
(int)$var

Incorrect:
(int) $var


Setting a variable should always have a space before and after the equals sign

Correct:
$var = 1;

Incorrect:
$var=1;


***
Whitespace
After any code, but before a new line - there should be no white space. The same is true for an empty line.

After the closing PHP tag it is extremely important to remove any white space.

***
New Lines

Opening curly braces do not go onto a new line, they will always have a space before and be on the same line.

1 True Brace Style (1TBS) ([WIKI](http://en.wikipedia.org/wiki/Indent_style#Variant:_1TBS))

Correct:

if ($my_example == 1) {

class ModelExampleExample extends Model {

public function addExample() {

} else {

Incorrect:

if ($my_example == 1)
{

class ModelExampleExample extends Model
{

public function addExample()
{

}
else
{


***
File naming
All files should be in lower case and words separated by an underscore.

***
Class & method naming
Class names and method names should be camel case.

Correct:
class ModelExampleExample extends Model

public function addExample()

Incorrect:

class model_exampleexample extends Model

public function add_example()


A method scope should always be cast.

Correct:
public function addExample()

Incorrect:
function addExample()


***
PHP Function (helpers) naming
Helper function names should be lower case and an underscore used to separate words.

***
PHP variable naming
PHP variables should be lower case and an underscore used to separate words.

Correct:
$var = 123;
$new_var = 12345;

Incorrect:
$Var = 123;
$newVar = 12345;


***
User defined constants
User defined constants are set as upper case.

Correct:
define('MY_VAR', 'My constant string value');

Incorrect:
define('my_var', 'My constant string value');

***
PHP constants
These types of constant (true,false,null) are set as lower case

Correct:
$my_var = true;

Incorrect:
$my_var = TRUE;

***
HTML / CSS rules
Class names and id's should be hyphenated and not use an underscore

Correct:
class="my-class"

Incorrect:
class="my_class"

Print this item

  OCE v1.10.0 Bugs
Posted by: villagedefrance - 07-24-2017, 11:47 AM - Forum: Bug Reports - Replies (4)

Please report possible bugs in version 1.10.0.0 here.

Print this item

Information Upgrading OCE
Posted by: villagedefrance - 07-24-2017, 11:35 AM - Forum: Installation and Upgrades - No Replies

----------------------------------------------------------------------------------------------------------------------
THIS IS FOR UPGRADING EXISTING OPENCART 1.5.x, 1.6.x, 1.7.x, 1.8.x, 1.9.x STORES ONLY!
----------------------------------------------------------------------------------------------------------------------

1. BACKUP YOUR EXISTING STORE FILES AND DATABASE!!
- Backup your database via your store Admin->System->Backup
- Backup your files using FTP file copy or use cPanel filemanager to create a zip of all the existing OpenCart files and folders.

2. Download the latest version of OpenCart Overclocked Edition and upload ALL new files on top of your current install EXCEPT your config.php and admin/config.php. If you are up-to-date with the last recent version and want to find just the new files that have changed since the last version, you can follow this guide to create a smaller changes-only patch. But for most, the full OpenCart Overclocked Edition zip will suffice.

3. Browse to http://<yourstore.com>/install Replacing <yourstore.com> with your actual site (and subdirectory if applicable).

4. You should see the OpenCart Overclocked Edition Upgrade script.
- If you see the OpenCart Overclocked EditionInstall page, then that means you overwrote your config.php files. Restore them from your backup first. Then try again.

5. Click "Upgrade". After a few seconds you should see the upgrade success page.
- If you see any errors, report them immediately in the forum before continuing.

6. Clear any cookies in your browser.

7. Goto the admin side of your store and press Ctrl+F5 a couple of times to refresh your browser cache. That will prevent oddly shifted elements due to stylesheet changes.
Login to your admin as the main administrator.

8. Goto Admin->Users->User Groups and Edit the Top Administrator group. Check All boxes.
- This will ensure you have permissions for all the new files.

9. Goto Admin->System->Settings
- Update any blank fields and click save.
Even if you do not see any new fields, click save anyway to update the database with any new field names.

10. Other Adjustments that may need to be made, depending on which version you are upgrading from and to.

11. Load the store front and again press CTRL+F5 a couple of times to refresh your browser cache. That will prevent oddly shifted elements due to stylesheet.

Note that some of your vQmod scripts may need to be updated for the new core changes.
So run through your site catalog and admin areas and check in FTP for the vqmod/vqmod.log file.
If you see errors, then you will need to address them.


Troubleshooting:
------------------------------
1. If you have any upgrade script errors, post them in the forum
2. If you have 3rd party addon errors, contact the mod author for an update.
3. If you find bugs, check the "official" bug thread for this version of Opencart Overclocked Edition.

Many bugs may have already been reported and fixes will be offered in the first post of this thread.
You should always visit this thread immediately after a fresh upgrade to see if there are any immediate bug fixes
If nobody has reported your bug, then please report it.


That's It!

Print this item

Information Installing OCE
Posted by: villagedefrance - 07-24-2017, 11:23 AM - Forum: Installation and Upgrades - No Replies

--------------------
CLEAN INSTALL
--------------------
These instructions are for a manual installation using FTP, cPanel or other web hosting Control Panel.

- Linux Install -
------------------
1. Upload all the files and folders to your server from the "Upload" folder. This can be to anywhere of your choice. e.g. /public_html or /public_html/store

2. Rename config-dist.php to config.php and admin/config-dist.php to admin/config.php

3. For Linux/Unix make sure the following folders and files are writable.

    chmod 0755 or 0777 image/
    chmod 0755 or 0777 image/cache/
    chmod 0755 or 0777 cache/
    chmod 0755 or 0777 download/
    chmod 0755 or 0777 config.php
    chmod 0755 or 0777 admin/config.php

    If 0755 does not work try 0777.

4. Make sure you have installed a MySQLi Database which has a user assigned to it.
    DO NOT USE YOUR ROOT USERNAME AND ROOT PASSWORD

5. Visit the store homepage e.g. http://www.example.com or http://www.example.com/store/

6. You should be taken to the installer page. Follow the onscreen instructions.

7. After successful install, the /install/ directory will be automatically deleted for security reasons.


- Windows Install -
-----------------------
1. Upload all the files and folders to your server from the "Upload" folder. This can be to anywhere of your choice. e.g. /wwwroot/store or /wwwroot

2. Rename config-dist.php to config.php and admin/config-dist.php to admin/config.php

3. For Windows make sure the following folders and files permissions allow Read and Write.

    image/
    image/cache/
    cache/
    download/
    config.php
    admin/config.php

4. Make sure you have installed a MySQLi Database which has a user assigned to it.
    DO NOT USE YOUR ROOT USERNAME AND ROOT PASSWORD

5. You should be taken to the installer page. Follow the onscreen instructions.

6. After successful install, the /install/ directory will be automatically deleted for security reasons.


- Local Install -
------------------
There are many all-in-one webservers out there and most of them should work with OpenCart out of the box. Some examples...

https://www.apachefriends.org/index.html
http://www.wampserver.com/en/
https://www.mamp.info/en/

Print this item

  Poss bug 1.94
Posted by: Xav - 06-28-2017, 12:30 PM - Forum: Bug Reports - Replies (3)

Hello,

I am using OCE 1.94, upgraded from 1.93 (and possibly from earlier ones).

Just looking at  Reports->Sales->Orders and there is nothing there when I put in a date range, despite having orders in the chosen period.

(Also same as with 1.93, it hasn't updated the region list to include London as an option).

regards,

Xav

Print this item

  Github Repository
Posted by: villagedefrance - 06-27-2017, 02:51 PM - Forum: General - No Replies

Opencart Overclocked Edition latest code is available at anytime.

Github Repository: https://github.com/villagedefrance/OpenCart-Overclocked

As the code evolves all the time, try to stick preferably to the published Releases as this can be easier to manage if you require support later on.

BETA and RC (Release Candidate) versions are suitable only for testing and developping.
Feel free to download them but I wouldn't recommend them for production use.

You can contribute to the project by Watching it, Starring it or Forking it.

If you find bugs or typos do not hesitate to open a new issue.

If you have made an improvement to the code, you can also submit a pull-request.

Not all issues can be fixed and not all pull-requests can be accepted, but all will be verified and not ignored.

Being a Community project means everybody can be part of it, so don't hold back!

Print this item

  Help us help you!
Posted by: villagedefrance - 06-27-2017, 02:46 PM - Forum: General - No Replies

If you are asking for Support, please provide us with the following information:

ESSENTIAL:
- Overclocked Edition Version Number.

OPTIONAL:
- Clean install or Upgrade.
- Server type (Apache, ...)
- Database type (MySQLi, PDO, ...)
- Database collation (utf8_general_ci, ...)

SCREENSHOTS:
Sometime a screenshot is the easiest way to describe a problem, so feel free to post a screenshot but please try to be reasonable with the image size!

In summary, the more accurate the information supplied is, the easiest it will be for us to investigate and the sooner you will get replies to your question.

Print this item

  Extension Store Comments are not for support!
Posted by: villagedefrance - 06-27-2017, 02:43 PM - Forum: General - No Replies

The comment system in the Extension store is not intended for support questions, and should only be used for the following:

- Pre-purchase Questions.
- Post-Purchase Testimonial, Reviews, or Constructive Criticism.

Support questions should be handled via email or other private contact disclosed in the readme file of the purchased extension. Since support questions are usually very specific to the individual user, it typically doesn't benefit other people who are trying to read through pages and pages of irrelevant comments. The extension system is also very basic, and doesn't have email updates for replies from the author, so that delays getting a fix until you manually revisit the site.

It is especially counter-productive when there are issues that have been resolved and people are still reading about them in the comments, leading to more confusion about outdated issues that no longer exist.

Only in the case where the author did not include a private form of contact with the mod should the comment system be used for support questions. You should also reserve your negative comments until after you've contacted the author to assist you. Most authors are very quick to support their customers, and most of the issues are usually fixed very quickly.

Negative reviews should only be given in the case where the developer has not responded to support questions and you are left with no alternative.

It is also very important and courteous to be sure to rate the mod after you've resolved any issues by clicking on the stars on the individual extension product page. Also if you rated it less than 5 stars because it was lacking features, be sure to update your rating later if the author adds the additional features you requested.

Print this item

  Forum Code of Conduct and Rules
Posted by: villagedefrance - 06-26-2017, 12:44 PM - Forum: Forums Usage Policy - No Replies

Common rules

- Only one account per person is permitted.
- Do not pretend to be/represent somebody else. Your account will be deleted if found to be in breach of this rule.
- When registering, a valid email address has to be used. Disposable email addresses are not permitted. If found, we will remove the account in question.
- Keep all posts on-topic.
- All posts must be in English, unless posted in a specific international forum. If posting in a international forum, please use the language of that forum, and not English.

DO NOT SEND SUPPORT REQUESTS VIA PM, unless expressly invited to do so. Using PM to actively solicit work is not allowed. Post, in accord with the rules in the correct forum.
Abuse of the PM system in this way can lead to your membership being removed.

- Do not discuss illegal activities.
- No useless posts. This includes: Thread bumping, useless one liners, repeated requests about new versions, Flamewars, Trolling and Spamming.
- Do not propose/link to any site that contains warez/copyrighted software/materials that can be downloaded illegally.
- Do not link to any site that contains adult content, sexually oriented material or might otherwise be considered offensive. Any post containing an inappropriate link will be deleted and the poster will receive a warning.


At all times

- Keep all commentary civil, and be courteous at all times. Constructive criticism is welcome, but insults directed towards other users or the site admins will not be tolerated. Coarse/insulting language will not be tolerated.
- Choose an appropriate subject line. Try to summarise the problem briefly in the subject, and elaborate in the message itself. A title like "Have you seen this..." or "Help needed!!!!" will be deleted.
- Spend 10 minutes with the admin panel before posting common sense questions like "How do I see orders", or "How do I add products". If you go through each admin menu you will find all you need to know about the basic features.
- Search before posting. You may need to search multiple variation of the terms.
- Any posts deemed to be self promotion, advertising, or spam can and will be removed. NO SPAM - NO ADVERTISING eg. Posting and making excessive, inappropriate and unnecessary references to your products and websites is self promotion.
- Don't lump sum mods and inquiries in one post. People asking for help and at the same time attaching a contribution should be avoided. Contributions go in the contrib thread. Help goes in one of the support threads, based on the affected element (modules, templates, languages, general, etc).
- Bugs go into the bug area ONLY after you have searched the bug forum and found nothing similar.
- Hijacking threads because you feel the need to whine or complain about your personal opinions that have nothing to do with the main topic of the thread will be instantly deleted at will!
- If you feel a post violates any of these rules, or you need to bring it to the attention of a moderator (move threads/close/split), please use the ‘report this post’ link to notify the moderators


 Signatures & Avatars

- Must be setup in your Profile (user Control Panel) , and not manually added to your messages.
- May not contain any pricing, sales, product etc. details.
- Only exact URLs allowed ie not LOOK HERE - No tinyurls, affiliate links etc either, only exact, literal URLs.
- Maximum font size should not be larger than normal +1.
- Signature shall not have more than 4 lines (at a line width of 75 chars).
- Any signature or avatar that is offensive or insulting to either us, our members, or our staff, is prohibited.
- Signature size should not exceed the maximum size of 60 x 180 px (height x width).
- Avatar size should not exceed the maximum size of 75 x 75 px (height x width).
- Signature & Avatar images may not contain any copyright material (e.g. trademarks).
- We reserve the right to ask you to change and/or remove your signature or avatar at any time, for any reason.


Failure to abide by these rules may result in an editing, negative moderation or deletion of your post.

We reserve the right to ban users from the site.
We reserve the right to change these rules at any time.

Print this item