2 new issues after github update

skyrun

Active Member
hadn't updated in awhile from github since my production app has been running well (a production app in f3.1 on j3.1!).

make a few other changes and decided to try the latest github in test and i notice 2 things that don't work now. this is only on my test system, so my production system continues to run well.

1) on this screen: http://www.skyrun.com/skyforce/test/campaigns when you click on a campaign name it shows the form without the proper .css. used to pop the form up in a window for editing. looks like it's putting a ?tmpl=component on the end of the link for some reason. the link is the default link (not a custom link) so i think fabrik is putting this on. if i manually remove the added ?tmpl=component from the url, the form displays fine on it's own page. (it used to display the form to edit the row in a popup box which was nice... but i would take it on it's own page too... never did figure out how to select which way to display it...)

2) my activity score list is creating bad sql. you can see it on the backend here:
http://www.skyrun.com/skyforce/test...php?option=com_fabrik&task=list.view&listid=5
or on the front-end here:
http://www.skyrun.com/skyforce/test/activities then click on a score, or on the id column (which puts the activity list on the bottom of the form in the footer.

all 3 places generates the same error on a bad column name being used in the fabrik-created sql. it's related to the two multiselect fields i have.... tried resaving the list and the multiselect elements to see if i could get the sql regenerated, but to no avail...
 
There's a couple of nasty looking Javascript errors on page load for issue #1, nothing to do with Fabrik, which I suspect are short circuiting the loading of our list / popup window handling JS. They seem to be coming from mod_asterisk. Try disabling that, get a clean page load with no JS errors, see if our stuff starts working again.

-- hugh
 
Hmmm, for issue #2, I think in fixing the old "repeat element in a repeat join" issue, we may have broken "repeat element in a non-repeat join".

This may take a day or three to fix.

-- hugh
 
We are in need of some funding.
More details.

Thank you.

Members online

Back
Top