Qbase Technologies » Blog

Migrating Drupal 7 Site Causes Internal Server Error on Images

admin — Thu, 09 May 2013 12:29:45 +0000

I recently came across an issue with my images not showing up on my Drupal 7 website after I migrated it from my staging server to the production server. It was just showing an X. When I looked at the image path, everything was correct and the image existed. I wasn’t sure what was wrong because everything was right. Some research said that it was an issue with the .htaccess file. I tried that, but that didnt work. But I did find a solution!

Solution: There was an extra .htaccess file in the /sites/default/files folder. Once I deleted that, all my images came back! I hope I’m helping someone.

The process of SVN

qbaseeditor — Tue, 22 May 2012 19:15:05 +0000

SVN is a centralized system, so you have one central repository. The first step is to create the repository
that your code will sit in. This will either be on your local network, a remote server, or third-party service
that offers repository hosting. This is, however, still classified as a remote repository, it just happens to be
hosted on a server you don’t fully control. Once your repository is created, you then do a “checkout” of the
code to a folder on your local machine. This is a copy of the remote code, which you can make changes to
as need be, without affecting the code in the repository.
Having one main repository allows for multiple people to take a copy of the same code base and
collaborate on the same code project. Now that there is a local version of the repository on your machine,
you can make any needed changes to it, including adding new files. Any number of files can be added to
the repository by using a number of methods, but until those changes are pushed to the main repository
they are only available to you. Once you have made any needed changes to the code or added any new
files, you would then “commit” the code to the repository. When you commit any files, whether they are
existing or new, you get the option to add a message. These can come in very, very useful when you
come to revert a file and wonder why it was committed in the first place. There is always the option to use
a message with no meaning or relevance at all, such as on http://whatthecommit.com; however, that
doesn’t help at all. Having useful commit messages is an asset to anybody using version control, and
getting into the habit of using them should be learned as early as possible. Once your message has been
added, the code will be merged with the existing code in the repository. If, however, SVN detects that
someone else has made a change to a file you’re about to commit, it will stop it and tell you to update to
the latest version of the code. This, of course, means you check for any changes to the central repository
compared to your local version. If it detects that you need to download new files, or new versions of files, it
will do that for you. If you do add new files and they are successfully committed, from now on, any user
that updates from the repository will get the new files. Although putting it into words can make it seem
complicated, it’s actually quite simple. Have a look at Figure below to see it in a nice visual format.

Of course, that only handles pushing updates and new files. What If something goes wrong and you need
to get back a previous version of a file your working on? Well, you can revert your local version of a file to
the version currently in the repository, or an even older version than the current one.
All of these actions can easily be managed with a SVN GUI on any of the main operating systems. In most
cases updating, committing, and reverting can be done by one or two clicks of a button, which makes it
very simple to use and manage, and also explains why so many designers and low-end developers like it
for its simplicity and ease of use.

Fine-tuning the UI by Theming Forms In Drupal 6.0

qbaseeditor — Wed, 02 May 2012 05:29:22 +0000

Thanks to Drupaldojo.com

A new stylish Theme for Drupal 7 TB Methys

qbaseeditor — Mon, 30 Apr 2012 06:05:35 +0000

Looking for a refeshment in Drupal theme? This maybe your choice.

Featured as a sub theme for Drupal Nucleus base theme, TB Methys is designed in simple and bold style: bold font set and wide slideshow. Furthermore, it supports multi-color skin tone, which gives more choices to customize the theme.

TB Methys comes with a set of features as you know from our Drupal themes. TB Methys is the first theme supporting multi-color serving for fashion and live style content.

Explore and see how powerful Nucleus could be.

You can get it here: http://www.themebrain.com/theme-detail/tb-methys

Guys – Well this is not a Post But Wallpapers for our Buddy Drupal

qbaseeditor — Thu, 26 Apr 2012 18:47:09 +0000

Summary flow of the node building sequence for a View operation

qbaseeditor — Thu, 26 Apr 2012 13:18:39 +0000

Thanks to IBM

How to Write Efficient CSS and HTML for Drupal

qbaseeditor — Mon, 23 Apr 2012 08:23:04 +0000

This session was given by Jan-yves Vanhaverbeke (aka jyve) and was focused on improving the quality of the HTML and CSS in a Drupal project. Which means removing unneeded Javascript and CSS of core and contrib modules and analyzing the graphical design to see which HTML elements can be styled with shared CSS selectors (also called Object Oriented CSS). Remove unneeded DIV’s in you HTML (a great tool that can help here is the 3D view in Firebug that shows all layers in the HTML) and make sure you design all common Drupal elements before you start implementing your design. So create a page with all common elements (links, headings, lists, image, etc) and make sure those are styled correctly (check margins line-height, etc). Then style all generic elements (header, footer, nav, colors and links). Optimize the HTML, for instance by using Display Suite and strip the default markup. A nice module that can help here is StyleGuide which add a tab to your Theme settings with a listing of all common Drupal elements including tabs, messages, etc.

Some good tips to keep in mind

Use generic classes above IDs.
Replace module specific HTML (date.css, etc).
Theme a semantic element, not a drupal module. So .article-teaser instead of .views-articles .views-row
Keep your CSS flexible. Work generic (.field instead of .page-article #content div.node div.field-title).
Dare to rework existing CSS as features are added.
Optimize your CSS using CSS standards (http://drupal.org/node/302199).
Use comments to add structure to your CSS
Compress cached pages (under performance settings).
Optimize your images.
Use image styles with Image Resize Filter
Use hook_css_alter and hook_js_alter to remove Drupal JS/CSS
Combine different CSS groups into one using hook_css_alter() and put them all in CSS_DEFAULT.
Finally, test your site with Yslow.

Thanks to Drupal Planet

Chat with the Drupal Community on IRC

qbaseeditor — Fri, 20 Apr 2012 06:43:00 +0000

The Drupal IRC channels are vital for connecting the community. Not only are they a great way to get fast, effective support, but they allow users to learn more and to get involved. Drupal uses the FreeNode IRC network, irc.freenode.net, and occupies the following channels, as well as these Regional IRC Drupal channels. Note that conversations on some of the Drupal channels are being logged.

Check the “Setting up IRC” page for information on how to get connected to IRC.

Essential Channels to Join

#drupal is a lounge of sorts. Here, we talk about patches we need reviewed, quick how-to questions, and what we’ve been doing with Drupal lately, among other things. If it’s Drupal-related, and isn’t in-depth enough to take over the channel with lots of text, and doesn’t need a quiet venue, it is fair game in #drupal.
#drupal-contribute is the place to go if you want to help with core and contrib coding work, promotion, advocacy, infrastructure, and general Drupal community tasks. The rule of thumb here: if it ends up on the drupal.org infrastructure, and you are working on it or want to work on it, then this is the place to talk about it.
#drupal-support is for long or deep support discussions. While quick questions are okay in #drupal, some discussions are just too long for that channel, or need a quieter venue — that’s when they go in #drupal-support.

Topical Channels

Note: There is a separate page for Regional IRC Drupal channels.

#drupal-accessibility channel to chat about coding and accessibility issues and extensions in Drupal
#drupal-adaptivetheme design and theme development support and discussion for users of Adaptivetheme.
#drupal-association Connect and collaborate with the Drupal Association.
#drupal-apps for collaboration around the Apps and App Server modules and the Open App Standard, as well as support for building Apps.
#drupal-codereview for the Code Review group, discussion of the code review process, collaborating on “New Project Application” code reviews, or to solicit assistance/advice/help while performing a code review.
#drupal-consultants for Drupal Consultants. You can find paid help here, as well as advice on best practices and general discussions surrounding the business side of Drupal. Ask questions here only if you’re willing to pay for the advice.
#drupal-coworking for Drupal Coworking. If you’re new to coworking or are already a coworking pro, this is the place to ask, learn and share information about collaborative Drupal coworking spaces.
#drupal-design for drupal designers. This channel is not for theme related talks, but pure design.
#drupal-docs for the Documentation team to discuss and organize working on the drupal.org handbooks.
#drupal-dojo for the Drupal Dojo group. This is where dojo lessons are discussed and organized.
#drupal-ecommerce for the E-commerce Group
#drupal-edu consolidates the various Drupal in Education related channels, including higher education, distance learning, elearning, k-12, training. See “Forming a Drupal in Higher Edu Consortium”.
#drupal-facebook for the Facebook API Group. All matters related to integrating Drupal & Facebook, whether through contrib modules or directly through the API, can be discussed here.
#drupal-features for Features support and discussion.
#drupal-fit for those interested in fitness-related activities at Drupal meetups, camps and conferences.
#drupal-geo for people interested in mapping, location, and geographic topics.
#drupal-gitsupport for help with using Git during and after the CVS to Git migration.
#drupal-groups for group organizers. Receive and give tips on how to organize a local Drupal user group.
#drupal-html5 for discussions on how to implement html5 with Drupal.
#drupal-i18n (i18n = internationalization) – discussions about making Drupal and modules internationalized (ready for localization)
#drupal-l10n (l10n = localization) – for Drupal translators, group managers and users of localize.drupal.org.
#drupal-ngo for open discussion on how people are using and can use Drupal most effectively for nonprofits and NGO’s.
#drupal-ostatus for anyone interested in working on bringing Ostatus to Drupal.
#drupal-pubmedia for discussions regarding Drupal in public media.
#drupal-seo for search engine optimization support and module development
#drupal-rdf for Semantic Web and Linked Data related support and module development
#drupal-services Development and support related to the Services module
#drupal-themes for in-depth or lengthy theme support discussions. If your theme work seems to be causing too much screen scroll in #drupal, or needs a quieter place then this is where to go.
#drupal-ubercart for Ubercart support and development
#drupal-usability for the Usability Team to discuss changes to the UI and general usability issues.
#drupal-vent is a place to share your frustrations with Drupal, core or contributed. Ever been driven crazy by a module and want to tell everyone about it but don’t want to risk hurting the maintainer’s feelings? This is the place to do it. Co-miserate with others in the Drupal community and let it all out. Keep the anger out of the main channels, out of the issue queues, and vent about it here. Lurkers are welcome. If you are a contributor and want to see if people are venting about your contribution, you are welcome to hang out here but please understand that the whole point of the channel is to vent and don’t take offence. Very important: This channel was created to vent about code, themes, docs, things like that, not people. If you have an issue with a maintainer, you should take it up privately with the maintainer.
#drupal-voip for Voice over IP Drupal discussion and support
#drupal-watercooler is a gathering place for Drupal folk to discuss non-Drupal things. It’s an off-topic area where we can chat without having to worry about being interrupted by wacky “work” stuff. All are welcome!
#drupal-wscci is home of the Web Services and Context Core Initiative (WSCCI) for Drupal 8. Mostly it’s discussion of that initiative, and a good place to hang out if you want to join in the effort to make Drupal 8 a web services powerhouse.
#drupalcon is the channel for people attending a DrupalCon; outside of that time, the channel is pretty quiet, but you might find DrupalCon organizers there.
#open_atrium for discussions about Open Atrium, an install profile for project management that is based on Drupal.
#drush for discussions about drush, the Drupal shell.
#aegir for discussions about the Aegir hosting system for Drupal

CK-ERP also for Drupal

qbaseeditor — Thu, 19 Apr 2012 12:46:12 +0000

CK-ERP is an open source accounting / educational / MRP / ERP / CRM system that runs on top of multiple middlewares. It comprises 32 modules – Contact Management, Customer Relationship Management, Customer Self Service, Vendor Relationship Management, Material Requirement Planning, Warehouse, Inventory, Service, Accounting Ledger, Bank Reconciliation, Accounts Payable, Accounts Receivable, Purchase Order, Sales Order, Quotation, POS for Cashier, POS for Manager, Human Resources, Staff Self Service, Payroll, Administration, Internationalization, Access Control, Data Import, Teacher, Counsellor, Student, Applicant, Family, Registrar, Edu Administration and Volunteer Management.

Link to goto ck-erp site: http://ck-erp.org/drupal/

Project are also downloadable at : http://sourceforge.net/projects/ck-erp/files/latest/download

New features include,
Support for Mysqli
Support for Sqlite3
Portuguese translation
Korean translation
Japanese translation
Hindi translation
Indonesian translation
Vietnamese translation
Russian translation
Updated Chinese translation
Updated Spanish translation
Updated French translation
Updated German translation
Relaxation of restriction on display language must be the same as
installation language

As far as I can determine, a Drupal+CK-ERP environment is most useful to
teachers, school administrators and other educational professionals.
While Drupal supports the front-end web communication between teachers
and students, CK-ERP provides facilities to manage backoffice routines
of the school. All these happen within the familiar Drupal processing
environment.

Example Modules for Drupal Module Developers

qbaseeditor — Tue, 17 Apr 2012 07:47:33 +0000

This project aims to provide high-quality, well-documented API examples for a broad range of Drupal core functionality.

Developers can learn how to use a particular API quickly by experimenting with the examples, and adapt them for their own use.

Drupal Module Developers who are really need to learn module development can use this project to download example modules for their reference . The examples modules link is http://drupal.org/project/examples