I was using joomla 1.5 on PHP4 recently my hosting provider updated to PHP5 then my joomla 1.5 crashed.
I have installed joomla 3.x
Could anyone please tell me the simplest way to convert a joomla 1.5 template to 3.x ?
Thanks in advance.
It really all depends on how complex your template is. If you have a simple template without a lot of overrides what I would do is treat your template like a PSD and just make a fresh template based on Protostar's blank slate.
Put your jdocs where you want them and create the basic less file with the basic colors, fonts, styles that you need.
Add the template parameters if you need them in a new XML file since some of that has change.
If you have a lot of overrides again you probably want to start from scratch by copying the new core layouts and modifying them to match what you had.
Custom JS will be the biggest pain point, but if you are still running MooTools 1 you really are ready to update that.
I used this : SP Upgrade and everything works fine except some minor changes I had to make because the 1.5 version was extremely customized. The most important thing for us was the content and template which successfully migrated.
Related
The current latest Joomla! v3.9.14 (August 2019)
The integrated tinymce is v4.5.11
Tinymce released the new V.5.0.0 in February 2019, including major improvements and a great new API
I want to use a plugin written with the new V5 API in Joomla!, so I wondered if it's possible to upgrade Tinymce to V5 in Joomla, or if we have no choice but to still use the old ugly Tinymce v4.x?
I tried to replace/edit files in media/editors/tinymce, just to see if it could lead to something, but of course it doesn't seem to be the right direction.
Rather than replacing the files (which could be overwritten in any future update), you're probably better off writing a new plugin for Joomla that installs Tiny 5.
The source code for the (v4) TinyMCE plugin is a good place to start to write your own - replicate how this plugin works, and you'll need to extend its functionality.
Doing it this way also means you could choose to use the Cloud version of Tiny, meaning you don't need to host the files locally, and receive updates as Tiny push them live. You do need a Tiny API key for this, but IMO, I feel it is a smarter way to host Tiny given that even during 5's life in 2019, some really useful features have been deployed, and if you're hosting all the files yourself, you'll need to keep updating them as you go.
The challenge with writing your own Tiny 5 Joomla plugin is that the core TinyMCE plugin for Joomla does not make it possible to have externally hosted Tiny plugins (such as a custom one you've created). So you would need to extend both the configuration and the instantiation to be able to store external plugin configuration, pull it in to Tiny's config, and also be able to manage your toolbars.
At Joomla Day Australia 2019 I spoke about developing external plugins for Tiny 5 in Joomla 4, and have a plugin that uses the cloud version of Tiny, and allows for external plugin configuration - but this was for an alpha version of Joomla 4.
Joomla 4 will come with Tiny 5, and I did a pull request to get external plugins in to the Editor config, so just waiting for Joomla 4 could be a more passive option.
Just trying to understand the working of com_content component in Joomla 3. Is it possible to disable or uninstall com_content component? Is it a core component that is essential for the functioning of the entire framework, so it cannot be removed?
You can't disable or uninstall any core components such as com_content. They are protected. I'm not sure of the exact things that require com_content, however completely removing it which would have to be done by deleting the folders and removing any reference to it in the database could possibly and most likely result your site malfunctioning. It's therefore protected for good reason ;)
I do know that in either Joomla 3.5 or 4.0, there will be an option to install core components with installing Joomla.
While there might be some benefits in making Joomla lighter, in the current configuration I would say that IS NOT RECOMMENDED to even try something.
Consider using ACL to hide it for the users that don't need it.
I know there exists tools that migrates Joomla to Wordpress at database level. But my problem is I don't have access to Joomla database anymore. I only have whole Joomla! 1.0.x site's local copy which was taken 2 years ago. Is it possible to migrate that posts to my Wordpress site?
Or should I copy-paste all content to a CSV file and use an Excel importer ?
Not specifically for Joomla , but I have made such a thing in the past several times while migrating from some Custom Cms's
It will depend on HOW BIG is your site and how much information you need to migrate (and it's complexity) but you can always go for HTML SCRAPPING / PARSING.
As from this point , GIYBF . And your Coding skills.
One of the best one IMHO is Simple HTML DOM ,and another that many recommend but I personally never used are htmlSQL And phpquery .
But there are also a lot of Tutorials on google ( here also and EXAMPLE TUT) explaining how to do it , and also a lot of questions here on SE and a list of options (not PHP exclusive).
The other option (which is basically the same , but without libraries) , is going or REGEX , like in this very simple example..
If you don't have the DB, then you don't have the content. All of the content on a Joomla site is stored in the DB. If you only have the Joomla files, there is nothing to copy and paste in to a CSV.
Try using this script. http://azeemkhan.info/2008/joomla2wordpress-import-wizard-v3/ Note you will need to install an old version of wordpress first and THEN upgrade your wordpress version.
There's a useful guide on this here and info on utf-8 support here.
Hope this helps
I am joomla user and I have created some extensions's and templates for joomla 2.5, but now I upgraded to joomla 3 because of bootstrap framework and responsive templates. I need your help here:
How to update joomla 2.5 extension to work with joomla 3 and be responsive?
I googled for a wile and couldn't find any answer about "extensions".
It's a big question, but here are some baseline steps.
First, make sure that your 2.5 code is clean. That is if you are still using any classes that were deprecated in 2.5 first go ahead and update them in your 2.5 version or else do that first in your 3 version. If you aren't logging deprecated classes you should do so to make sure you don't miss any. In particular you want to get rid of JRequest and look for any methods you might have extended that themselves extended JObject and make sure you are not relying on those methods. Also, you need to make sure you have changed any extends JModel to extends JModelLegacy (and similar for JView and JController). Depending on the complexity of your outputs you can likely follow the core code as a model for your administrator layouts. For the front endin my experience you are mainly just changing layout files to use the newer classes and ids.
If you use the Component Creator to develop your component framework you can specify if you want to build Joomla 2.5 or Joomla 3.0 compatible code.
Since 2.5 is the current LTS version until 3.5; the majority of the core changes are deprecated versus being completely removed. Meaning you can still use them and there are overall not many things required to migrate a 2.5 component, for now. I would definitely read through the walk through provided by Soren, but here are the three "major" required changes to get a 2.5 component working on 3.1 and above Joomla... with caveats of course! :D
1) Make sure all your view classes extend JViewLegacy
2) Make sure your primary controller extends JControllerLegacy instead of JController
3) Make sure your primary component entry point (my_component_name.php file in component root) use JControllerLegacy::getInstance('my_component_name') instead of JController::getInstance('my_component_name')
I'm working on NopCommerce 2.60 and I have extended Affiliate Module in NopCommerce 2.6 by adding two new fields like "WebsiteURL" and "Picture Upload".
For that I have made changes in Affiliate Services, Affiliate Controller, Affiliate.cs, Affiliate Map, Affiliate Model files. Now If I want to integrate these changes in upcoming versions of NopCommerce.
So What is better way to make changes in NopCommerce code and easily integrate in upcoming versions of NopCommerce?
There is no any way in nopcommerce to upgrade custom functionality in higher version. instead of that i would suggest right you function independent to nop means write separate classes for all Affiliate functionality, copy it in next version as you see in nopcommerce2.65 they have change some service, properties name.
I have recently looked into this since our company wanted to make sure nopCommerce could be upgraded at later dates if needed. The best solution we found was to make our modifications into plugins so that we could refrain from modifying the core as much as possible. Like Shivkumar said, it's not really possible to make nopCommerce upgrade proof.
Hope this helps.