[Issues Solved!] Trials and Tribulations of Upgrading to Composr

A diary of successes and lots and lots of failures

Ok quickly…

side_users_online, a bug if session_prudence option was enabled - fixed.

Other issue due to caching needing clearing after base URL change (shouldn't have been needed - bug fixed) - works now.

Thanks so much! I now got my site fully updated to Composr (v10)! I know this was a huge upgrade due to the rewrite and all, and surely future upgrades won't be so painful.

Thank you again Chris. I hope that this thread has proved at least somewhat helpful in tracking down upgrading issues so that everyone can benifit from it.

And now, some pics to show off all the hard work, and one to show off my favorite feature of Vivaldi.
null

Today I tested out importing a Wordpress Blog.

In one of my classes (I am currently in my final year for my associates degree in Database Admin and Programming - dual major), I was forced to make a WordPress site for a final project. It was in my Web Programming class, and despite the case I made for using ocPortal to truly demonstrate my grasp on php and mysql, the professor wasn't convinced. So I had to make a WordPress site with several pages and several blog entries. Yuck.

Anyway, today I tested out how well Composr imports such things.

Importing via putting in website location failed - I was greeted with a lovely stack trace and an error screen. BUT! Importing via database was a success, for the most part. It did not import any comments made (there were some) despite me telling it to do so. But it did import the blog posts I made including pics.

Ok thanks.

I saw an error mail for viewing catalogues RSS from you, and just fixed that.

The RSS URL import was a bug fixed earlier, should be fixed in latest RC.

Not sure about why DB import of comments would fail, but maybe the comment system used isn't the default, or Wordpress has made a change somewhere.

Why bother reporting issues to the tracker if they are simply closed with no reason given? I request that if you close an issue, to please make a note as to why to help prevent the feeling of simply being ignored so not to discourage future bug report submissions. Bonus points for linking to the duplicated issue so it can be noted that the issue is known about and is being worked on.

Also, is there a way to check for existing bugs in the tracker?

I did leave a note, you have the "Simplified attachments UI" option enabled, which removes the options for configuring attachments in favour of making image uploads very simple.

You can search for issues from: View Issues - Composr CMS feature tracker

My apologies, I did not see that note when it got closed. On a side note, never make bug reports when you have a day altering headache.

It's okay, sorry you have a headache. I will actually take a bit better of a look at that issue later. While you were racing the system you did manage to generate some error messages, which should not really be possible. Maybe we need to lock the editor mid preview or something like that. But the gist of it is, advanced users likely will always want to disable that option.

You have no need to appologise, I was out of line.

But, the issue still presets after disabling that simple attachment function.

I got the attachments fields back, but now I still can't make the options, it automagically sets thubmnail for me. And this time I can't race against the clock so to speak, to open up the attachments properties dialog, only getting the link image dialog.


Maybe there's yet another setting I need to toggle?

Ah, you need to edit the ATTACHMENT_UI_DEFAULTS.js template.

I decided this was annoying the other day and edited it already, so you can just grab and use the latest with no override:
https://raw.githubusercontent.com/ocproducts/composr/master/themes/default/javascript/ATTACHMENT_UI_DEFAULTS.js

Empty the template cache after replacing the file though.

Yes, that fixes my issue. Thanks!