Cannot Save Changes To News Items

[kbemis]

I have CMSms 1.7.1 installed and running without many issues, everything seems to be working fine, with the exception of one seemingly major issue...

I imported news items from an existing CMSms installation, a 1.0x version (I can get the exact version number, if required).  There are no issues loading an news items for editing and when saving.

Then I clear the cache, and review the "edited" news article to find that no changes have been saved.

If I go back to the news administration screen, the "edited" news article appears with none of the edits.

Any idea what's going on here or how I can begin to debug this?

Thanks.
~k

[calguy1000]

I imported news items from an existing CMSms installation, a 1.0x version (I can get the exact version number, if required).  There are no issues loading an news items for editing and when saving.

News has no 'import' functionality, so exactly what did you do?... I think I know, but I am not gonna guess.  For what seems like the the 4,123,583th time I'm going to ask for complete information so that SOMEBODY ELSE can respond.

I'm done responding to crap posts like this.

[kbemis]

The word import implies that I worked within CMSms, which I did not.  I copied the database tables from the existing 1.0 install to the new (1.7.1) site.

And seriously, nobody forced you to reply.  If you're done replying to "crap like this", you shouldn't have replied in the first place.

[calguy1000]

This user obviously hasn't read the forum clearly marked 'README FIRST'.
didn't follow forum rules on the post
and posted in an official board, potentially asking for a response from a dev team member... at least in a board that is monitored, and moderated by the dev team.

[kermit]

database schema can change from version to version, and from 1.0.x to 1.7.1, there's many changes that have been made to the cmsms database structure. you cannot simply copy specific tables from an old version to a new one and expect it to work.  you can, however, often replace an entire database old to new, then run the 'upgrade' script on the new one to update the database schema.. sometimes a huge jump in version has some issues....

@calguy: would it have hurt *that* much to have provided an explanation instead of just ranting like usual? sheesh...

[calguy1000]

@kermit: yes.