fixed bug with new article route