I recently upgraded an old store from 2.0.1.1 to 3.0.3.8 but to comply with PHP8 I need to upgrade again from 3.0.3.8 to 4.x. My question stems because I was able to successfully install the new 4.0.1.1 storefront, but I am no longer able to access my admin panel. Attempting to login to my admin will always give me the error that the account does not exist.
I have double checked the config.php files in both my root & admin folders and the database information stored there is correct. Also, I checked my actual database to make sure the user accounts weren't deleted in the upgrade and they were not.
I don't see a lot of documentation about the upgrade process to a 4.x OpenCart storefront so I am coming here in hopes someone has been brave enough to attempt this upgrade that may be able to point me in the right direction. Some tips and tricks would be greatly welcomes because I imagine this is just the first of many moles I am going to need to whack.
Let me know if any code would be needed/handy, but keep in mind this install is basically all stock barebones at this point because I haven't even tried to activate my custom theme yet (mostly because I can't access the admin to activate it).
Solved this by upgrading to the OpenCart 3.x.x_Maintenace branch, instead of OpenCart 4.x.x version, as it is also PHP8 compliant and much more stable.
For anyone with similar issues, they can refer this link.
Related
I'm in a brain-breaking problem here. I've created a nice Magento 2.1.7 installation with two websites (two stores, two domains) and somehow after a while we are unable to login the backend of Magento.
Invalid Form Key. Please refresh the page.
Now, after trying a few options, still no success. Checked core_config_data, edit max_input_vars, nothing works. The strange thing is, on the front it's still possible to checkout and do your shopping.
Anyway, I'm stumped here. Why is this happening, and how can this be fixed. Any help is welcome.
I often get this error, clearing the cookies for that site, then opening the admin panel in a new tab will resolve this.
You can recreate this error message if you double click the login button after filling out your login information.
Here are a few other reasons you may experience this issue
The form key inputs are outside of the form, you should check the html on the admin panel to check these inputs and exists and have correct values
Make sure the link you use to get to the admin page does not already have a form key in the url
Does this issue generate anything in var/log/system.log ?
Eventually, nothing helped, but what did the trick was creating a new install, setup this new install with all necessary modules (fortunately there were only four), configure the fresh installment like the old one (long live GitHub) and compare your fresh installation to the old one in the database table core_config_data. Basically reproduce your entire setup without any products in it, but just create your stores and categories.
If you spot any differences between the new installment and the old one in the core_config_data, edit them in the old one to be the same as your new one.
Next, edit your env.php with the database credentials to the old database which you've compared and edited.
And the last step, recompile, flush/clean cache and reindex.
Oh, and word of advice, if you're going to use https for your store, setup magento on https. I think something went very wrong when we've changed the base url's from insecure to secure.
I recently did a successful Django install, and everything went as expected. No errors. But, nothing shows up. It is as if I had never installed Django.
There are no errors. Checking Django/Python versions returns as expected. From the console, I can create new projects/apps, run migrations, create users, etc. Everything seems to work. Except, when I go to mydomain.com, it just loads the old site's index.html as if Django doesn't exist.
I realize the above question isn't a good question. I figured out my problem before posting the question and decided to post my answer below with the question for future reference should others have the same issue later.
After the fruitless task of deleting and recreating my project files, I eventually figured out what happened with my Django installation. I had never enabled Passenger. On the web host in this case, DreamHost, it is just a simple checkbox in the control panel to enable, but I never did.
Other than the fact that I should have remembered I need to do enable Passenger for Django to show up, a couple things should have tipped me off. There was no tmp folder with a restart.txt file. I manually added it (that file's important), but didn't stop to think about why it wasn't there. Also, the html files were loading without being in the public folder.
That gave me an hour or so of frustration today, so I thought others might google this later and find this useful. Searching for "Django site has no errors but still doesn't work" wasn't a fruitful avenue for me.
First time user. Installed Prestashop 1.6 last night locally on my computer (I want to try it out before I commit to it). However when I got to the admin panel it had the same presets as found in the demo version (http://www.prestashop.com/en/demo).
So, figuring I may have just somehow, accidentally downloaded the demo version, I uninstalled and reinstalled just a few minutes ago. Yet, lo and behold, I get the same presets. Is there anyway to do a reset on the admin panel so that I get a clean slate (no orders, customers, stats, etc)?
Downloaded Prestashop from the homepage. Used this article (blog.dh42.com/installing-prestashop-locally/) to download it locally.
Here is your solution : http://www.prestashop.com/forums/topic/320579-delete-all-sample-data/
Go to your back office
Modules
Search for cleaner
Install pscleaner module
Use this module.
Another solution here : PrestaShop: Delete all testing data before production
I'm trying to upgrade our Web Forms For Marketers to the latest available on SDN, however when I come to install I get the follow exception throw:
Could not find configuration node: databases/database[#id='production']
However, this is correct so far as the only databases configured are Core, Master and Web.
I tried adding a production node (pointing to Master) to Databases.config/ConnectionStrings.config however it still throws this error.
Has anyone encountered this and has a solution?
The error is telling you it cannot find a <database> node in your web.config for "production" so you'll need to have that. Something you have must be referencing that.
The problem lies with a bug in Sitecore not correctly cleaning and rebuilding the Links database.
Sitecore Support provided this solution:
Back up.
Truncate the links table in the Core database.
Rebuild Link Database from the Sitecore Control Panel.
This seemed to solve the issue in the short term. I'm sure it'll be addressed in a Sitecore update in the future.
We've got a company wiki running Mediawiki on our intranet that has been in use for a while. We just recently installed Redmine and are in the process of getting it configured just the way we like it.
I was wondering if there's any way to use our already existing wiki instead of the built-in one that comes with Redmine. We've got alot of articles & documentation written by non-developers and don't want to lose and/or re-import into another wiki (ie redmine's). The Wiki portion of redmine will not allow me to enter the url for the external wiki as it includes various illegal characters (mainly : and /)
Edit: As a temporary work around, I've just used each project main page on the "external" Wiki as the Projects "Home Page" in Red Mine, so far this is the best I've been able to figure out. You don't get Wiki access from the various issues & what not, but the link to our other Wiki does show under the Overview for each project now.
Btw, both of these are installed on the same physical box, a Windows 2003 Server, where Mediawiki was installed using a WAMP package, and Redmine was installed pretty much manually instead of using a stack like Bitnami.
Did you see this MediaWiki integration patch for Redmine? http://www.redmine.org/attachments/572/redmine-mediawiki.patch and its reference page http://www.redmine.org/issues/617 I have not used it so im not sure if it meets your needs but it might be worth a shot. (Be sure to backup first)
The reference page says this about the patch:
Here's a patch for 0.7 that will add a
MediaWiki tab to your project settings
and integrate it into the issues
pages. You will also need to add:
is_mediawiki tinyint(1) NOT NULL
default '0', mediawikiurl
varchar(255) NOT NULL default '',
mediawikinamespace varchar(255) NOT
NULL default ''
To the projects table for this to
work.
I know you didn't want to import but just in case someone else did here is a rake file for importing MediaWiki pages into Redmine http://www.redmine.org/issues/1224
We looked into this as an option since there are so many tools that work with mediawiki however we decided not to pursue the option since we already had so many issues and wiki pages in redmine. As far as I can tell, this patch replaces the existing redmine wiki input boxes with mediawiki boxes. This is done not only in the wiki section but also for issues and documents. We were afraid of:
Losing all of our existing wiki pages, and issue descriptions.
The whole thing breaking as Redmine updates are posted and installed.
We have found that the newest Wiki Extensions plug in http://www.r-labs.org/projects/r-labs/wiki/Wiki_Extensions_en has given us most of the features we wanted for the wiki part. It has comments, voting, tags, and many other things. It works well with the latest version of Redmine.
We still are trying to find a good way to import into the wiki all of our existing documentation from word.