I couldn’t login to Application Designer today for some reason. I kept getting an “Invalid User ID and password for signon.” error despite my credentials being correct.
It turned out that adding the EOPP_USER and PAPP_USER roles fixed the issue:
1: Navigate to the user’s profile (PeopleTools > Security > User Profiles > User Profiles)
2: Enter the user’s ID and press search
3: Select “Roles” from the top row of tabs
4: Add the “EOPP_USER” and “PAPP_USER” roles
5: Press save
I finally decided to replace all my existing code to handle images with Paperclip. I was following the screencast by Emerson Lackey, #134 Paperclip, however I ran into a couple of issues. Thankfully they were all very easily fixed, and probably wouldn’t have occurred at all if I’d simply watched the whole screencast instead of trying to rush on ahead.
Issue #1:
The first issue I encountered was that my asset fields weren’t appearing on the page:
I spent way too much time trying to work this one out, especially considering how obvious the solution is – the screencast is simply missing an “=” after the initial “<%" in "<% f.fields_for". Simply amend it as follows:
Issue #2:
The second one is actually encountered and addressed by Emerson himself. Unfortunately I started trying to find a solution before seeing his, so just in case someone else does a Google search I’ll include the issue here:
undefined method `symbolize_keys!' for "/system/assets/1/original/mack_truck.jpg?1329550205":String
The problem here is simply that the parenthesis are in the wrong place, simply amend your code as follows:
Anyway, hopefully this helps someone else out – let me know if there are any issues.
Update: Don’t name your model assets!
Unfortunately I followed the tutorials naming example and called my model Asset. While this may have been fine in earlier version of rails it causes quirky conflicts with the asset pipeline. I strongly encourage you to use a different name i.e. Uploads
I’ve recently switched from SQLite3 to PostGreSQL and came across the following error this morning:
my_app_development=> select category from codes; ERROR: column "category" does not exist LINE 1: select category from codes;
The following post solved the issues in one sentence:
http://archives.postgresql.org/pgsql-novice/2007-01/msg00032.php
Yes. In postgres, unquoted column and table names are converted to lower case.
The user also added that when using PostGreSql you should either be always, or never using quotes around column names.
Just a quick problem I came across in SharePoint today when trying to edit a file:
The folder structure being used was fairly complex, unfortunately this meant that a filename only had to be a few characters long to exceed this rule. Unfortunately there does not appear to be an easy way to fix this issue other than reorganizing the folder structure.
One workaround is to simply press the “Open with Explorer” button and edit the file that way. Thankfully the url limitation does not effect files reached through this method.
This link has a bit more info for anyone who may be interested.
I ran into a bit of a problem today after implementing a search form that appeared on every page. When the login page was loaded I received the following error:
The weird thing about this is that the route my search form uses does not mention devise in any way:
'products', :action => 'search', :method => :get do %>
As you have probably already guessed, I’m using devise to handle my authentication. Unfortunately this seems to be overriding some of my routes whenever it co-exists with another form. Luckily there exists a very simple, although hard to find solution – simply add a forward slash before the controller definition:
'/products', :action => 'search', :method => :get do %>
Here’s a quick link to the StackOverflow post which gave the answer, hopefully a few more links to it will make it a little easier to find for anyone else out there doing a search!
I ran into a bit of a problem with a has_many relationship in rails today:
This turned out to be a fairly simple fix, I had forgotten to add a has_many relationship before adding the has_many :through => x relationship. There is a fairly detailed explanation on StackOverflow for anyone who is curious.
While trying to do a migration today I received the following message:
#After running a trace (rake db:migrate –trace)
undefined method `to_sym’ for nil:NilClass
/usr/lib/ruby/gems/1.8/gems/activesupport-3.1.1/lib/active_support/whiny_nil.rb:48:in `method_missing’
…
This was the migration:
class AddDefaultValuesToFeedbacks 0
change_column :stores, :rating, :decimal, :precision => 8, :scale => 2, :default => 0
end
end
Unfortunately this problem also prevented me from performing any other migrations on the table. I attempted deleting all relevant migration files and then re-running them, restarting the server and rolling back to a previous migration – none of which worked.
Eventually I resorted to exporting the dataset, dropping the table via sqlite3 and recreating it. Thankfully this seems to have worked. The only hint I’ve come across that may explain the cause of this problem, other than typos or referring to non-existant columns, is that it can occur if a migration is screwed over before it finishes and fails to rollback properly.
If anyone else has any concrete answers, please let me know in the comments!
Ran into a bit of trouble with a model today, after a bit of a google I came across this technique which helped me solve it:
#Raise exception on object.inspect raise Object.inspect #Example 1 raise order.inspect #Example 2 raise [sub_orders.count].inspect
This simply allows you display variable values as an exception. By placing a few of these throughout your troublesome code you can simulate a fully targeted trace.
Ran into the following error when trying to open a word document stored on SharePoint today:
Unfortunately this appears to be an issue with Chrome, once I switched to IE it all worked fine.
Ran into another flash notice issue, my messages were not disappearing after the first view. My code was as follows:
#Create flash warning
flash[:warning] = ("This product has been replaced: " +new_product.title + "").html_safe
It turns out that all you have to do to fix this issue is the following:
flash.now[:warning] = ("This product has been replaced: " +new_product.title + "").html_safe
This blog gives a brief overview of when to use flash.now[notice] and when to use flash[:notice]. A basic rule of thumb is that if you’re using a redirect, use flash[:notice], if you’re simply rendering a view, use flash.now[:notice].
What I Broke - Programming and Web Development 