hello,
i have following problem: when editing article, when hit "save" or "save & close", "save failed following error:" --- but no error shown , changes article saved.
the site problem observed on offline version preparing upgrade live site running 1.7.1. because have made changes template code, cannot perform standard upgrade without destroying entire layout.
therefore, made fresh install of 2.5.6 on wampserver, manually rebuilt categories (100+) exported actual articles , imported them via sql.
the problem observed on exported/imported articles, written in either english or bulgarian.
the exception articles published under "Новини" (news) category, first-level category. @ first thought problem occurred second- , third-level categories found out occurs on other first-level categories, seems irrelevant.
the problem not seem occur newly written articles.
the db table structure identical between 1.7.1 , 2.5.6, , anyway, didn't import errors don't think relevant either.
please if can.
edit: research did prompted me looking @ asset_id article has in #_content table , respective id in #_assets table. after experiments, found out non-matching ids are not causing problem. successful saves matching asset_ids , non-matching. , error both matching , non-matching asset_ids. ... more puzzled.
i have following problem: when editing article, when hit "save" or "save & close", "save failed following error:" --- but no error shown , changes article saved.
the site problem observed on offline version preparing upgrade live site running 1.7.1. because have made changes template code, cannot perform standard upgrade without destroying entire layout.
therefore, made fresh install of 2.5.6 on wampserver, manually rebuilt categories (100+) exported actual articles , imported them via sql.
the problem observed on exported/imported articles, written in either english or bulgarian.
the exception articles published under "Новини" (news) category, first-level category. @ first thought problem occurred second- , third-level categories found out occurs on other first-level categories, seems irrelevant.
the problem not seem occur newly written articles.
the db table structure identical between 1.7.1 , 2.5.6, , anyway, didn't import errors don't think relevant either.
please if can.
edit: research did prompted me looking @ asset_id article has in #_content table , respective id in #_assets table. after experiments, found out non-matching ids are not causing problem. successful saves matching asset_ids , non-matching. , error both matching , non-matching asset_ids. ... more puzzled.
Comments
Post a Comment