I am developing a site based on Drupal CMS and it has awesome image managing tools but there is a problem: While the images are being nicely resides rotated or else their paths become a bit weird for a common user.
It just so happens that users will see a lot of my images urls and I want them to look short, nice, and pretty. Since there is powerful module called Pathauto for Drupal users I just thought that changing masking files original url could be as simple as nodes.
Could it be that easy? If so, how? Maybe there is more than one way to do it? Could some non-Drupal way do the job?
You could try editing the htaccess file. It seems someone else has had that same thought... Drupal alias your file paths using htaccess
Related
I'm using a multisite setup in Drupal 7. I'm wondering if it's possible to limit where a site can look for which modules to use. For example, there are a lot of modules I'd like to be able to use across all sites (../sites/all/modules/). But I would like Site A to have access to modules/custom/siteA, but not modules/custom/siteB.
Is this possible or do I have to share all modules across all sites?
You're thinking of it the wrong way; going depth first instead of breadth first. This is one of the "benefits" to going multisite.
In Drupal 7, you should be able to put any modules you want only to appear to a specific site into it's sites/site-name/modules/ directory; site-name being whatever directory you mapped the sites/sites.php file to go to for the given URL. I think you should already have a settings.php file in your sites/site-name directory. Just add the modules folder and dump them in. I'm not really sure how to handle it further, or how to install site-specific modules from the site GUI (if that's possible.)
I only put benefits in quotes because I've never been a fan of going multisite, but plenty of people have been more than happy to and it's worked out great for them.
this is quite easy. Suppose there are two sites you have created with multisite installation.
Site A (root site)
Site B
The modules that are common will be placed in sites/all/modules directory. But you can define some modules to appear in the site B only by placing the same in
sites/SiteB/modules.
I hope, it is making sense for you. Otherwise feel free to ask your queries.
All the Best!!
I'm trying to convert the theme from Drupal to Wordpress, I don't know a lot about drupal, so this function "drupal_get_private_key" confuses me a little and I can't really find a lot of documentation about it. Could someone explain me what is this function about and how could I do this in Wordpress?
Thank you for the help
Drupal uses this to generate the paths to files* (its used in other stuff too, but in themming I believe its the main reason).
*These files are the files created by users, not the files in the theme folder. The folders are configured in the admin and, when an user uploads a news picture, for example, it will be placed in the configured folder.
You problably just want to find another way to find these paths.
We are looking to run one website using two CMS systems, so for all the content related stuff it would be drupal, and then for all the ecommerce related stuff, we are looking to use Magento.
Do you think this is possible? What are the general thoughts on this as an idea?
Usually we would have the ecommerce on a subfolder, like /store/productname... however, the client has specifically asked that we don't have it on a subfolder, hence asking for opinions on here.
Edit: For the sake of anyone thinking this is not programming related, I am wondering if there is something that you could achieve with the .htaccess file (rewrites etc).
I don't think this is really possible, both Drupal and Magento rewrite all incoming requests for non-existing files to index.php in the root.
I guess you could change one of the CMSs root files to index2.php and try to route requests for that CMS to the correct index file. However this means you will need to maintain a list of all paths that can be accessed by that particular CMS in the .htaccess file itself, which would be a real pain.
I have an mu install with the typical blogs.dir folder storing files for each blog. When loading these images however they take forever to appear, but they eventually do. It seems that wpmu uses php to serve each image which is ludicrous. When using images from the same domain but in a root folder, the images are displayed quickly.
Is there a workaround the blogs.php for rendering files?
Could there be something else wrong in the settings of my install?
Hard coding the Rewrite Rule instead of using blogs.php is a temporary workaround with huge speed differences. This can only work if you already know the blog ID's.
I'm converting a Wordpress blog to Drupal and need to map the WP paths to the new Drupal ones.
What's the best practice for doing this? There are only around a hundred pages to map. I've been experimenting with the URL Alter module, which provides an alternative to messing with custom_url_rewrite functions settings.php but keep getting 404. Waiting to hear back from the module maintainer if this is what the module is intended for. In the meantime I am wondering how others do this? Should I be using .htaccess?
Maybe this page could help you to merge your wordpress blog into drupals with WP2Drupal.
You can use Path_Redirect to catch the old URLs but still use PathAuto to give them new URLs; GlobalRedirect will make it even more transparent