I want to increase the size of a field in the joomla database (table jos_menu, field link). Any idea what will happen to it when a new version of Joomla comes out and I do a Joomla upgrade? Will the field gets resized on upgrade, hence losing some of my stored data? How do I prevent this?
Thanks in advance.
(Joomla 2.5.x)
Your tables should be fine with minor updates however you never know if Joomla will require changes to the #__menu table in the future. Lots of changes were made to the database structure in Joomla 1.6 so what's to say it won't happen in Joomla 4.0 (when released). I would say you should be ok when changing the size of the field but every time you update Joomla, just double check that none of the changes have been reverted.
Related
I inherited a Magento store from another developer who tried to customize the default theme and made a mess of things. I'd like to install a fresh template but need the default theme back in its' original form (without the customizations/modifications made by the previous guy). There are no backups available for me to roll back to.
Is there any way I can download and re-install the original, unaltered Magento default theme, or do I need to start with a fresh installation of Magento to obtain this?
There is no solution that I know that comes out of the box regarding templates rollback (as there is not for rolling back sql table schemas...).
You can get the version of the Magento via Mage::getVersion() and it should also be displayed in the footer of the admin panel.
From there, you can download any version of Magento from Magento's website and overwrite the whole directory app/design/frontend/default/default and/or app/design/frontend/default/base depending on the version.
You don't have to get the whole Magento to a fresh install... But chances are, that if the template is that a mess, you could also have to deal with core files modification (the worst) and may want to actually start from a fresh Magento install.
Hello
I have a live Magento 1.8.1 site where pagination was working on product list pages (such as category pages) but I’ve been adding and removing a number of extensions / plugins and I’ve lost all pagination. Unfortunately, I can’t remember the last time it was working so I can’t think precisely what extension might have caused the problem.
I’ve checked all the usual fixes such as here but my catalog.xml is fine (and all problems seem to only relate to 1.4 - 1.6). I am reluctant to upload new files which I actually think might fix it but I also know how temperamental Magento is! Everything else is working perfectly for the first time after a month of serious hard work including a couple of reinstalls!
The website is next2new.net and although you can see a custom theme, there is also no pagination on the default magento theme which indicates to me it’s a core problem somewhere.
Any thoughts on any files I could check / change before I do a big overwrite?
Many thanks
Following things you can try in order to Cope-up with this situation :
1) Disable those modules which is overriding Catalog module and check once again.
2) Check whether Toolbar block is calling or not using Template and Block Path hints using Magento Admin.
3) If you are using any template, possibly there could be a setting in Admin section to Manage toolbar.
Recently I ran into a problem regarding Re-index in Magento.
My store has around 40,000 products and If I change a status of a single product, changes are not reflected on frontend as it needs reindexing of all Indexes.
Moreoever reindexing takes a hell lot of time (around an hour) and I am thinking of a permanent issue.
What does "Save on Update" mode in Reindex specifies ? Does it help in reindexing while saving the product ?
Whats the difference between manual update and update on save ?
Please help.
Thanks in advance.
I assume you mean "Update on Save" when you say save on update, also called as "realtime" mode which triggers the re-indexing of product data every time the product has been saved / updated.
Basically in Magento there are only two modes of re-indexing "Update on Save" (Realtime) and "Manual". Their names speak their mode of behavior quite clearly.
In your case, as you have huge amount of products in your store, do the re-indexing through Magento SHELL commands like the following which in turn saves you a lot of time.
SSH to your store and go to shell folder inside your magento root and re-index one by one or all in one shot
php indexer.php --reindex catalog_product_flat
php indexer.php reindexall
Use the "Update On Save" re-indexing mode, it will do re-index on the fly for that single product you have saved.
The magento manual (http://docs.magento.com/m2/ce/user_guide/system/index-management-manual.html)
States:
Set Actions to “Reindex Data.”
Its too bad the options are not available! Do you see those options in your admin pages? If not, is there a reason why it might not show up?
I would like to do update on save, but this is not really practical. I imported a large number of products from CSV.
I tried running the re-indexer from the command line, but by shell directory is missing.
magento missing shell directory
Well, it looks like I am fresh out of ideas! Maybe I should just pay Varien to run Magento Enterprise for me. Afterall, re-indexing is a bit complicated, isn't it?
I was finally able to upload product images to a website using magento 1.7.0.2 but the images only appear on the front end and not visible via admin panel. I find it rather strange. Can anyone please tell me how to fix this? I have flushed the cache and reindexed several times but no apparent change.
I know this is an old question, but we had the same problem just now.
It seems that the import we did (the .csv file), missed a few fields, therefore entries were missing in the media_gallery table in Magento.
We couldn't repeat the import again, because the customer has already entered new and fixed a lot of the imported products.
We followed the guide here (thnx MagePsycho) to get the things sorted.
The guide needed a litle bit of fixing (manually entering the table names) since we were doing the fix on Magento 1.8, and had a bit of trouble with the table prefixes.
We are using Joomla 1.5.21 and JCE 1.5.7 and have some trouble with the front end saving of articles.
Saving the article in the front end has no effect on the article stored in the database and therefore users on other devices cannot see the modification.
However, the changes ARE visible for the logged in user even after deleting the cache & cookies and reloading the page.
I noticed this behaviour only when the user is classified as an editor or publisher, if he is an author the editor doesn't store any of the changes!
How can I get the article changes to save?
Thanks Salem for your comment but finally we could solve the problem by ourself. The problem was caused by joomfish or more by my OS. I am using a german OS which sometimes switches from english to german on its own, so that we had two different (language) versions in the back- and frontend.