How do I migrate Image Gallery from Drupal 6 to Drupal 7? - image

I have a Drupal 6 site that I'm trying to migrate to Drupal 7. However, I have a gallery using the Image and Image Gallery modules.
I know that Image is a dead end from Drupal 6, but the Image nodes can be converted to CCK ImageField fields uning the Field Converter module.
However, a migrationpath for Image Gallery seems to be largely forgotten, or at least I've managed to find almost nothing about it on the web. I think my best option is to roll my own gallery with Views, but I would welcome any tips for bringing my images from the Drupal 6 site.
Thanks,
James

Same answer as Drupal 6 To 7 Migration
You can use the Migrate module, or even better the Migrate D2D examples which should handle a clean migration for you with the ability of rolling back a migration if any problem occurs. A great way to fine tune a migration, when necessary.
With Migrate, you can migrate your files first, then migrate your Content Types by mapping the various field values. It takes a bit of getting into but once you get the hang of it, you'll love the simplicity & flexibility.

Related

Why do I need to compile Bootstrap instead of using the CDN in Laravel 8

I'm a graphic designer who just started learning Laravel this week, recently I've been searching how to install the latest bootstrap version in my project correctly, which is all I need to be honest and I'm not too comfortable with other options like Tailwind.
As some tutorials and answers have suggested I ended up compiling and using a famous project named laravel/ui, sadly the resulting version comes with a few changes, that just doesn't look as good in my opinion (different fonts like Nonito, colors and margins)
So now I'm wondering...
Why is it not recommended to just add the CDN links in my master template?
Is it possible to update this compiled CSS somehow to make it look as the CDN?
Sorry if this questions might be opinion based, but I'm really out of places to ask, seems like the documentation for Laravel 8.x has removed everything related to Frontend, which are making thing even more confusing for me with all these options Laravel offers.

Using Sage in a website that needs to be maintained by mere mortals

I am trying to help out an organization that hired some developers to create their website back in 2016, and the developers haven't touched the site since 2016.
I don't know enough about Sage to know if the developers really screwed things up, or if what they have done is the way things need to be done in Sage. One example of something that has me scratching my head (in between banging it on my keyboard): some page content - content that needs to be updated on at least a yearly basis - is hard-coded into template files, so that in order to update the information, you have to go in past the warnings about using the Theme Editor, figure out which included template contains the content, and update it there.
NOT something your typical office employee is likely to be able to do, yes?
My question is: is it even worth trying to keep this site running under Sage, or should I rebuild the site using a more user-friendly template? The site currently has fewer than 2 dozen pages plus a dozen or so posts and I would say is unlikely to get a whole lot larger, given the available resources.
Thanks for any advice you can offer.
The problem to me doesn't seem to be so much about the Roots Sage theme framework, but that the developers didn't follow the most basic rules regarding WordPress theme development--separating the content from presentation. Hardcoding content into a template is just bad practice, and this would make any site difficult to edit no matter what framework it was built on.
If it's as simple as printing the content into a template so that page editor content changes can be reflected on the frontend, it may be a simple as adding the_content() to the corresponding page template overrides and removing the hardcoded content.
FWIW: Sage 8 templates are not that different from your standard WP templates, it's not using a templating engine like Blade, so you should be able to customize the templates if you're already familiar with standard WP templates.
So probably no need to burn it all down.

Does Laravel have something similar to Drupal Views and Display Suite?

I recently taught myself the ins and outs of Drupal, became very familiar with Views and Display Suite, and am considering hiring a small development team to build a Guitar Lessons paid membership site for me in Laravel.
I will be creating the content for the site, and don't want to spend much time messing with the site. I need to focus on guitar playing. So the site needs to let me control my content in an efficient way. I need to be able to create views and choose fields and formatting (e.g. recent lessons, similar lessons, etc), as well as have flexibility in where I place views (on a sidebar, etc).
So, that said, are there plugins for Laravel that will enable me to do this or something similar? I mean I can code PHP and write MySQL queries, but I can't imagine creating/editing views at the PHP/MySQL level every time I want to tweak something.
Thanks!
In that case you do not need Laravel (why you think of using it?). Stay with Drupal.
If you really need Laravel for some reason, try to use OctoberCMS, which is based on Laravel. Or ask team hired by you to build custon CMS for you.
In Laravel you must code to add or modify views.

Joomla to Wordpress migration from HTML files

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

TYPO3 - creating a community site

Okay. This is the main functionality of my site. Here goes:
People register. They upload a list of whatever ebooks, movies, tv shows they have. Other people who want them will just have to 'search' for an item and they will be provided with a contact form to contact a person that has what they want. Very much like pianofiles.com but this is for a local community.
Added features could be
*forming social groups by interest
*creating events
etc..
Is all this possible using Typo3?
If yes, then how should I use Typo3 for it? (Just a basic idea)
If not, what should i use to create something like this?
Check out the TER, a quick search revealed http://typo3.org/extensions/repository/view/community
You could realize your project with any well known CMS or PHP framework.
TYPO3 CMS, as I see it, has a strong emphasis on the editor backend. If you don't need that at all and don't have any prior experience, I'm not sure if it's the right tool for you - unless you want to get into TYPO3 anyway!
PS: For TYPO3 web apps, there will be the upcoming Framework http://flow.typo3.org, wich is in beta

Resources