Options below are disabled in our Drupal UI
Aggregate and compress CSS files
Aggregate JavaScript files
I'm new to Drupal and I need a direction where to look on that problem. We want to enable both options.
our environemt is
Drupal 7.2.3
hosted on Amazon Linux AMI
Your directories probably have the wrong permissions set - go here admin/config/media/file-system to check your configuration and make them writeable.
Related
I am looking for a solution in episerver to add media files from external sources into episerver.I am aware that episerver has recently released Episerver Content Management API to post contents within Episerver.Is it possible to use this for media files as well.As this is newly introduced in episerver, i cant find any references other than the documentation within epi which has more of CRUD operations on Content.Can someone please point out some reference links for me to get this started?
Any input is appreciated.
Regards,
The content management API is useful if you want to create a headless website that talks to Episerver via an API to get content.
Depending on what you want to use the media for will depend on the optimal approach. I assume you want the content editors to be able to pick these items from within the CMS? If so there are two main appraoches:
You could write a scheduled task using the content repository API to import the media into the Episerver media library
The other option is to create a content provider, so the media is available in the editor, read this to learn how to do it. This option is more fidley so I would go with option 1 if possible.
If you just want to render images on a web page, then call the API using AJAX. Job done!
I would like to extend Kylo user interface. From documentation, i understood that I can use Plugin mechanism to add new features and I am referring to the examples available here.
I have built this example code and deployed the generated jar files to /opt/kylo/kylo-services/plugin folder and restarted the kylo-services.
But I am dont see any changes in the UI. As per my understanding, there should be a new group in left hand navigation pane but there are no UI level changes in the kylo UI.
I am using dladmin userid and logs (kylo-ui and kylo-services) really did not indicate any error.
Where can I see if the plugin is really picked up by kylo? Which logs tell me what is going on with this plugin? Any suggestions will be of great help.
Thanks
Gana
The mistake i did is copying kylo UI into /opt/kylo/kylo-services/plugin folder.
The generated jar files should go into different plugin folders.
Kylo Services plugin should be copied to /opt/kylo/kylo-services/plugin folder.
Kylo UI plugin should be copied to /opt/kylo/kylo-ui/plugin folder.
service kylo-services restart
service kylo-ui restart
And its my bad that i mistakenly copied kylo-ui plugin into kylo-services folder. After I copied into correct folders and service restart, I am able to find the UI changes.
Thanks for your attention.
We need to create the index.html for the mobilewebapp on Mobile Frist project dynamically on server side.
It's possible to use javascript or java to create index.html ?
Or the only way it's to load a html fragment calling an Adpter ?
In MobileFirst Platform Foundation 7.1 the index.html file is generate when you create the project in MobileFirst Studio. The feature you want is not available built-in.
You could build this feature yourself to create the file and place it in the in the project programmatically and then invoking the build and deploy steps programmatically as well.
In v8.0 you create the HTML file yourself (there are no projects anymore). Here it is simpler to create this file and handle it as there is no deployment required other than registering the app - once.
I suggest that you will look into v8.0.
I want to migrate all views from my local site to another site.
I know there is a module "Migrate" which allows you to do data migration but I don't know how to use it.
Can you give me some tips?
Thanks in advancej
Not sure what you mean with migrating views to another site. In Drupal, the migration concept is usually associated with actually migrating data - a view is actually just a way to query and display this data.
Typically moving a view to a different site, assuming data structures are the same in both can be accomplished by either exporting the view (one of the options while browsing the views on admin/structure/views) or, if it's not just a one of, by featurizing it which is a process that takes a few more steps.
It's only applicable for drupal site to drupal site
First download features module and enabled in both sites.
Go to admin-structure > features > create feature.
In that you can see General information(left side) and Components(right side). The General information provide some name in the name fields and you can see views in Components. You just select what are all views are needed for that site.Click the Download feature button.
It will downloaded!!!
After that copy the downloaded file to new drupal site which has drupalroot > sites > modules.
Go to your "new drupal site" as (Admin-Structure > feature). You can see the folder name as list in that. Enable the folder name list and click "Save settings". After the save setting finished as good then deselect the folder list, click "save settings" and delete the downloaded folder in module folder.
Note:
The folder name list should not state as conflict. If it presents, then click the recreate button.
I am using socialengine as content management system, when i change the socialengine site to production mode it did not load the css file, I figured out that my $staticBaseUrl function is not returning the website name.
I manually added the path in default layout to load the css file, it works but a font family (centurygothic) is not loads. I am using SocialEngine's 4.2.4 version, please help.
I am using plesk panel for as hosting server.
If you use paths in your css file (theme_name/main.css or Modulename/externals/styles/main.css), you can use following way of indicating path:
~/application/..., where ~ will be automatically parsed and replaced by staticbaseurl.
Firstly no need to manually adjust the $staticBaseUrl in the layout. There is a setting in the admin panel (general settings) where you just specify what the URL is. This is commonly used to set the CDN URL.
Secondly, most of the CSS files in production get minimized and appended to each other, so you will only see one query similar to this: /application/css.php?request=application/themes/default/theme.css
Thirdly, if there is still an issue there may be a number of reasons. For example, are you using the http://example.com/home or http://example.com/index.php/home URL format?