I have Drupal 7 set up on my OpenShift account using the Drupal 7 quick start. I have set up WinSCP to navigate the directory, and I can get to app-root/data/sites/all/, which is where custom Drupal mods go. I've installed the Zen theme as well.
However, when I try to change any of the template files in app-root/data/sites/all/themes/zen/templates, none of the changes show up at my site's publicly accessible URL. I've tried clearing the Drupal cache and the browser cache, but still it doesn't work.
At other hosts, I've never had this issue with Drupal. This problem seems specific to OpenShift. Any idea what's going on? Am I working in the wrong directory? Do I not have access to the live files?
Related
I have a website built on WordPress platform. Today, when I opened the website and when I clicked anywhere on the website, adult site pages are opening up continuously.
Can anyone please suggest what could be done to resolve the issue?
Your site is hacked by someone and some script injected in your WordPress installation or database which causing to load this video your website need to scan your website using plugin like SECURI You can get this on Securi.net
Here are some solutions that you can try(Remember to take a backup before using this)
Check and clean all your recently modified files
Contact your hosting provider if you are not using dedicated server.
If you have some inactive themes and plugins which you don't need more remove them.Hackers can hide script there.
-You can upload new word-press core files which you haven't customised.
Install fresh copy of themes and plugins if you not customised them.
Change your secret keys in your wp-config file.
Check users in your word-press and delete suspected ones.
Check permission of your installation directory .if not secure them make changes.
Change you WordPress password
If this all not works to solve problem let me i will look into it.
I'm using Drupal in a multi-site environment. I want to create a theme only visible for this site. So I created the folder sites/site_url.be/themes/theme_name. But the theme doesn't appear on the admin/appearance.
I have already a custom theme installed in the sites/all/themes directory, which works fine, and compared all configuration files.
I added the css, js and templates, so it is not empty.
Rebuild the cache several times using drush and the interface
Changed the permissions of the directory
I placed the theme in the sites/all/themes
Checked the ip of the interface in the browser, so I certainly work local
You can find the answer in the following link: https://drupal.stackexchange.com/questions/198081/drupal-8-theme-structure-for-multi-site
If you want to check that you have configured and set-up everything correctly for your multi site: https://www.drupal.org/docs/7/multisite-drupal/multisite-mapping-with-drupal (Drupal 8 is at the end of the page)
Goal: We have a Magento installation which contains a lot of sensitive data. We're looking to host a Wordpress installation.
Problem: Since we're installing third-party modules on Wordpress, we don't want any security issues in Wordpress to be able to compromise Magento.
I've spoken to a couple of my friends, and also had a think back to how it's been implemented in the past, but I wanted another opinion.
Since the wordpress directory will reside inside of the magento directory, would it be sufficient to chown the files inside of wordpress to a new user ("user-wp"), and then to chroot the user-wp user to the wordpress directory? Magento would then still have access to all of the Wordpress files, but not vice-versa.
Any other suggestions on how to go about implementing this would be more than appreciated! Somebody also suggested configuring a separate vhost.
Using a subdomain like blog.site.com would probably be the easiest way to set this up. All you would have to do is add a new VHost for the WordPress installation.
I don't think Chrooting would provide much security. You may also run into WordPress Plugin issues with such a configuration.
The setup is tricky. You would have to go and modify the PHP-fpm process pool and users it runs with. Then assign one pool to Magento and another to WordPress. Additionally you will also want to serve static assets & uploads from the Webserver itself.
And when you change this config you have to retest your Magento install to make sure things you didn't break anything accidentally.
Too much hassle, just use the subdomain. :)
Hi I am currently developing an Wordpress site offline on local server and want to upload to my domain online. I don't need to transfer the database, but I would like my pages, theme, widgets to work correctly.
What I am doing:
Copying Wordpress directory to domain directory through ftp.
Exporting everything in local server Wordpress and importing in
online Wordpress.
All my pages/posts are transferred, and my theme is installed but not set default. When I select it, everything is set to the themes original defaults, not like changed on the local server (for example tagline, background, etc). Also the widgets are the default settings.
Am I doing something wrong?
I am using Wordpress 3.4.2
Thanks!
Yes, you have just forgotten that some options for your themes are actually stored as WordPress options, so if you don't upload your database, you will not transfer these settings.
I've written a tutorial explaining step-by-step how to transfer a WordPress site to another server: http://www.sebastianbroways.com/wordpress-transfer/
If you follow each step the site should retain all the settings, including the template preferences. Good luck.
I have a new client that I am converting over to Drupal from Wordpress. We have two domains with the same name but different TLDs i.e. .com & .org. We have decided to start by setting up the site first under the .com so we have a live site to play with during the development.
So we currently have a wordpress site running on the .org and drupal (on a new host) running on the .com domain.
So two questions:
Can and How do you configure Drupal to work for both the .com and the .org ?
Can and How do you change the base domain drupal is configured with after the site is live ?
If you aren't using Drupal's multisite system (that is, the site information is being put into sites/default instead of sites/example.org or sites/example.com), this is really easy: do nothing. There is no step 2. Drupal will handle any domain thrown at it: just use your web server's name-based handling to determine which domains to accept.
If you are using Drupal's multisite system, it's a little harder:
Rename the sites folder (so from sites/example.com to sites/example.org).
Drupal's files table hardcodes the files directory it uses, so you're going to need to change all the paths in it. Run UPDATE files SET filepath = REPLACE(filepath,'example.org','example.com') on the database.
The other place to change the path is under Site Configuration -> File system.
The final place you're going to need to change paths is going to be on the settings page for your theme if you decided to use a custom logo or favicon.
Once you've changed all the paths, rebuild the cache under Site Configuration -> Performance.
This should cover most cases. Check with the third-party modules you're using to see if they also hardcode filepaths. If the modules are using the API correctly, they should've been handled in steps 2 and 3.
Because of all the hardcoded file paths, I highly recommend not using multisite unless you really need to. If you are only running one site in a Drupal install, just stick the site in sites/default.