My Opencart store has stopped importing orders to ShipStation ever since I updated my Journal theme. I know I probably have to update OpenCart which I am hiring someone to do but I need a workaround till then. Thank you in advance.
I get this error from ShipStation:
"An error occurred attempting to update orders: Invalid XML. Error: 'There are multiple root elements. Line 3, position 14.' We received: ' Journal Installation Error You are using an outdated OpenCart 2.x version. Journal only works with the latest Opencart 2.x version.Please download and install'"
The error log on my Opencart shipstation backend says this:
2016-07-20 12:27:06 - PHP Notice: Undefined offset: 1 in /home/garagist/public_html/store/shipstation/controller/export.php on line 23
Journal support said this to fix it and I have no idea how to do that:
You need to edit /shipstation/config.php file and add this line (anywhere in it), so the Journal engine won't be loaded for that extension:
define('BLOCK_JOURNAL', true);
First you installed the wrong version of Journal. I am very familiar with it and I know the developers provide a template for each version in the zip file from codecanyon. Even if you were running 1.5x, it's in there. Fix that problem first.
Second, ShipStation has nothing to do with journal, you have server issues now (probably due to the incorrect version of journal). I've never had to block journal from the ShipStation config file. That's probably why it isn't working.
FYI, I have around 5 shops and over 10 clients running journal and shipstation, no isuses at all ever. Versions range from OC 1.5-2.3.0.2.
You don't need to upgrade, don't pay if you don't have to.
Update: From Journal Directly "Compatible with Opencart: 1.5.4.x / 1.5.5.x / 1.5.6.x / 2.0.x / 2.1.x / 2.2.x / 2.3.x" Seems counterintuitive to support 2.0x if they're going to force you to update your OC installation when the theme is installed doesn't it?
Good luck.
Related
Currently I using OpenCart v2.3.0.2, after me purchased the theme template, I tried follow the documentation but stuck on here.
Before met this errors, I get some similar error, which is
/var/www/html/public_html/catalog/view/theme/logancee/template/extension/module/featured.tpl on line 2
at the end i solve this error by deactive and active the extension. Now I stuck on the footer.tpl, which is this error.
Notice: Undefined variable: registry in /var/www/html/public_html/catalog/view/theme/logancee/template/common/footer.tpl on line 2
Notice: Undefined variable: registry in /var/www/html/public_html/catalog/view/theme/logancee/template/common/cart.tpl on line 2
Notice: Undefined variable: registry in /var/www/html/public_html/catalog/view/theme/logancee/template/common/header.tpl on line 2
Please advice me if you face this kind of error before.
You can end notices in the settings by setting Display Errors to No. Or you can back-trace these errors and variables and fix them accordingly.
The theme you purchased is not prepared to handle some of the extensions, you have already installed.
I suggest you remove ALL extensions, modifications & vQmods that you have added and start adding them again by testing one by one to find out which one is giving you the error!
Also remove all your cached content & files before each step including your browser's cache.
Last week I upgraded from Sitecore 8.0 Update 5 to Sitecore 8.1 Update 2.
I ran into one issue where the SwitchMasterToWeb.config example included with Sitecore 8.1 Update 2 does not seem to include a patch to delete sitecore_list_index. This patch does exist in Sitecore 8.1 initial release???
Without the patch, this error is thrown (https://kb.sitecore.net/articles/347205) Manually adding the patch removes this error. Was the removal of the patch an error on the part of Sitecore? Or is there something I need to do to avoid this error from being thrown?
I also note there does not appear to be a patch to remove: sitecore_marketingdefinitions_master I would think that should also be removed with SwitchMasterToWeb.config. Is there a reason that reference to a master index was not patched?
I agree with Jay that SwitchMasterToWeb.config has never been implemented without noticing a few issues.
The reason you get that error is because there is no 'syncMaster' index update strategy is usually deleted along with all 'master' database indexes. That may have been deleted in the SwitchMastertoWeb.config file as well. Check to see if this exists in the file -
<indexUpdateStrategies>
<syncMaster>
<patch:delete />
</syncMaster>
</indexUpdateStrategies>
Deleting 'sitecore_list_index' may also cause you some issues. The issues caused by deleting 'sitecore_list_index' maybe the reason that Sitecore left it out of SwitchMasterToWeb.config file. Here is an issue caused by deleting 'sitecore_list_index' - http://sitecoreunleashed.blogspot.com/2015/07/sitecore-8-update-3-cd-servers-and.html.
To get around the issues above, we set the index update strategy of 'sitecore_list_index' to 'onPublishEndAsync' instead of deleting it.
<index id="sitecore_list_index">
<strategies>
<strategy ref="contentSearch/indexConfigurations/indexUpdateStrategies/onPublishEndAsync" patch:instead="strategy[#ref='contentSearch/indexConfigurations/indexUpdateStrategies/syncMaster']"/>
</strategies>
<locations>
<crawler>
<Database>web</Database>
</crawler>
</locations>
</index>
You can even try to set the indexUpdateStrategy to 'manual' instead of onPublishEndAsync and check the logs for issues. Manual strategy only builds an index when you tell it to via code or from the Sitecore interface.
To read more about Index Update Strategies, try this link - https://dev.sitecore.net/sitecore_experience_platform/setting_up__maintaining/search_and_indexing/indexing/index_update_strategies
To this day, I have never been able to launch a site (without errors) using the out of the box SwitchMasterToWeb. It always seems to miss something that was newly introduced, or is in a subfolder that patches in after, or some other reason.
You have most likely identified a bug in the SwitchMasterToWeb file for 8.1 Update 2 and should log a ticket with Sitecore identifying the issue. In the meantime, you'll need to deploy your own patches to resolve the issue. If you provide this to Sitecore in your ticket, they could then use that for future fixes to the SwitchMasterToWeb.
It is also possible that Support has already received this issue from another client and may have a patched SwitchMasterToWeb to provide you for your usage.
I just upgraded a client's test installation of Sitecore to 7.2 (SP1) and now, any image that has an underscore in its name is throwing a 404 error when being referenced by a page. This was actually a series of upgrades from 6.4 so it's quite possible that a config setting somewhere got missed along the way, but I don't see anything standing out at me that would cause this problem.
If I change the image name to not have an underscore, it works fine, and it also works fine if I set "Media.UseItemPaths" to false, but they would prefer it if their image URL's had the file name displayed.
Can anyone help identify what may have gone wrong?
Due to a change in Sitecore 7.1, any replacements specified in encodeNameReplacements are now also applied to media items as well as regular items in the content tree.
One option is to remove the replaceWith="_" declaration, but the likely reason this was added was to possibly replace spaces in your URLs so they do not display with %20. Removing this declaration will mean they return!
You can instead apply the fix specified in this Sitecore Knowledgebase article: Sitecore is unable to open media items when using encodeNameReplacements
I recently upgraded PHP to 5.4 and after adding some tweaks now the old osCommerce installation of a customer with lots of customisations is running again, but there is still a problem:
if you put an item in your cart the cart stays empty
How can I fix this?
Is there a certain php value I can set in php.ini so the session is working properly?
What I have tweaked so far:
Problem: all prices are 0 and there is no currency
Solution: adding !isset($currency) || in the paragraph `//
(see $currency not set in application_top under PHP 5.4 )
Problem: register_globals is REMOVED as of PHP 5.4.0
Solution: I simulated register_globals with this: https://serverfault.com/a/547285/128892
and I added this to includes/application_top.php:
// Bugfix PHP 5.4:
$HTTP_USER_AGENT=$_SERVER["HTTP_USER_AGENT"];
$HTTP_ACCEPT_LANGUAGE=$_SERVER["HTTP_ACCEPT_LANGUAGE"];
$HTTP_HOST=$_SERVER["HTTP_HOST"];
$SERVER_NAME=$_SERVER["SERVER_NAME"];
$PHP_SELF=$_SERVER['PHP_SELF'];
$HTTP_GET_VARS=$_GET;
$HTTP_POST_VARS=$_POST;
register_globals();
comment out this line:
#ini_get('register_globals') or exit('FATAL ERROR: register_globals is disabled in php.ini, please enable it!');
also I had to correct some removed functions in includes/functions/sessions.php: session_unregister() and session_is_registered()
Problem remaining:
Items filled into the cart don't get added to the cart. seems like the session isn't known in the add_cart page.
I've had the same problem. Found by comparing my 2.2ms2 code with rc2a version.
In application_top change
$cart->add_cart($_POST['products_id'], $cart->get_quantity(tep_get_uprid($_POST['products_id'], $_POST['id']))+$quantity, $_POST['id']);
to
$cart->add_cart($_POST['products_id'], $cart->get_quantity(tep_get_uprid($_POST['products_id'], $_POST['id']))+$_POST['quantity'], $_POST['id']);
I cound not fix this last problem, so after trying diffenent attempts I decided to take the effort and convert the shop with all its customisations into oscommerce 2.3 which still runs on PHP 5.4 (up to PHP 5.6).
Note that later, to get oscommerce running on php7 you'll need another fix for mysql functions to fix problems like Undefined function mysql_connect()
I know, I know, the first thing you are thinking is to check all of the instructions online and on dajaxproject.com
Well I have checked and checked and rerun this installation and I cannot figure out what the problem is. I assume it has something to do with the version of Dajaxice I am using and the version the installation instructions are, but those details are usually missing.
At this point in the process, I have everything setup to accomplish a very simple task. Load a webpage from the IP:8000 (ie 1.2.3.4:8000) and have that page load a simple html form button. Once that button is pressed, the page should then send a mesage (using dajaxice) to the server, and once it returns an alert box will pop up, proving that the dajaxice install is working.
So, I have:
Installed Dajaxice (and dajax for that matter), by getting the zip from here: github [dot] com/jorgebastida/django-dajaxice/
Changed everything in a basic Django project to follow the details in this tutorial: http://django-dajaxice.readthedocs.org/en/latest/installation.html
I have setup all of the details of ajax.py, and index.html to work with this example: django-dajaxice [dot] readthedocs [dot] org/en/latest/quickstart.html
PS Sorry for the "[dot]"s, but being a new registered user they limit you to 2 per post, so I tried to give you the best links clickable.
I am stumped. I have been trying many different things, but the documentation available seems so sporadic. It's gotta be something simple I am messing up, but I cannot seem to find it.
Currently, the "Say Hello!" button shows up on the screen, but nothing happens when you press it. Any ideas?
Here is a link to the zip file of the Django project I am working with here: https://docs.google.com/open?id=0B5rzYk6W5HlrYk9veVRfM3JkTGc
The way I have it all organized, DjangoAjax is just the folder containing the Django project. ajax_prac is the project, and practice is an app. Also you'll see a folder called django_media...that's pretty self explanatory, it just holds all the "media" for my Django projects, including jquery.js and jquery.dajax.core.js
If there are some details that I have smudged in the code, contrary to the installation guide, I apologize. I have been working through so many iterations of this, that it is likely I could've forgotten to change something back when making this post.
Can anyone help?
All the documentation weirdness is probably related with the new release I made yesterday (8 hours ago). Probably you was using an old version of dajaxice reading the new documentation.
I've release django-dajaxice (0.5) and django-dajax (0.9.1), both fully compatible with the last version of Django (1.4.1).
django-dajaxice: http://pypi.python.org/pypi/django-dajaxice
django-dajax: http://pypi.python.org/pypi/django-dajax
For this release I've also rewrite both documentations and hosted them on readthedocs. Also, http://dajaxproject.com code is now opensource so everybody can read the code and see how dajaxice works in production.
django-dajaxice: http://django-dajaxice.readthedocs.org/en/latest/
django-dajax: http://django-dajax.readthedocs.org/en/latest/
example project: https://github.com/jorgebastida/dajaxproject.com
Could you please upgrade to django-dajaxice (0.5) follow the new installation steps (quite similar http://django-dajaxice.readthedocs.org/en/latest/installation.html) and post here any traceback/issue you could have?
Thanks
In your example code ( DjangoAjax / ajax_prac / templatedirectory / practice / index.html):
<input type="button" value="Send message to server!"
onclick="Dajaxice.ajax.sayhello(my_js_callback);">
Should be:
<input type="button" value="Send message to server!"
onclick="Dajaxice.ajax_prac.practice.views.sayhello(my_js_callback);">
I.e. It must reference a Python module that contains your registered Dajaxice view. And according to your sample code, ajax_prac.practice.views exists while ajax.sayhello does not.
Also the Python module must be prefaced with "Dajaxice" (which is probably a significant source of confusion).