Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7726281
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 1, 20262026-06-01T05:10:27+00:00 2026-06-01T05:10:27+00:00

I use subversion to manage my yii website (php framework) and have separate backend

  • 0

I use subversion to manage my yii website (php framework) and have separate backend and frontend webroots for my application with the following paths:

/trunk/dev/backend/www/...
/trunk/dev/frontend/www/...

Now when I update a file in the frontend, e.g.

/trunk/dev/frontend/www/css/styles.css

… I can commit changes no problem. However, for some reason, subversion thinks that the corresponding file in the backend is exactly the same as the frontend file and doesn’t treat them differently, e.g.

/trunk/dev/frontend/www/css/styles.css = /trunk/dev/backend/www/css/styles.css

… even if the backend file is vastly different. If I update subversion, no differences are identified – it’s as if they are one and the same file.

I don’t think it’s my subversion client, because I am seeing the exact same behaviour in both Coda (my normal web authoring tool which is svn savvy) and Cornerstone (my specialist svn client).

I admit I am far from a subversion expert, so don’t know if it is not good practice to manage similar application paths in one repository, but I wouldn’t have though that my situation was unique. I am scratching my head, so any ideas would be greatly appreciated.

One thing that may be significant (and I think I may have cottoned on to what is going on…) is that the styles.css file is compiled automatically from a compiled LESS file:

/trunk/dev/frontend/www/less/styles.less
/trunk/dev/backend/www/less/styles.less

Could it be that the LESS compiler (codekit) is not generating the css file in a way that subversion recognizes? BTW, I want to include my compiled css files in my repository (for reasons that probably aren’t significant to this question).

I am using subversion v1.6 if that helps. Thanks in advance for any help 🙂

EDIT: I’ve updated the paths to show how they relate to my repository (trunk). My working copy pulls from ‘dev’ which is a subfolder under trunk. I’ve tried to reproduce this problem to describe the symptoms better, but of course, now it works without a problem (Murphy…). I don’t want to waste anybody’s time on this, so will come back if the problem reoccurs and I can give more information.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-01T05:10:29+00:00Added an answer on June 1, 2026 at 5:10 am

    Think I know what happened – found out that my ‘backend/www/css/’ folder (generated by less) was somehow ‘switched’ and was pointing to the ‘frontend/www/css’ folder. I’m guessing I did this somehow in my svn client (Coda or Cornerstone) without being aware of it, hence the strange symptoms where updates were not being reflected as I suspected.

    Have removed the switching and everything is back to normal (phew!). Thank for those who took the time to look at this, I know it was an odd one!

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'll set the scene first... We use Subversion and currently have a reasonably large
Do you use Subversion while developing a website with drupal ? I'm not talking
We currently use subversion as our version control system, we have decided that we
I have a subversion repository under /var/svn/ I am trying to use subversion to
I am tired of having to manage projects manually. We use subversion for version
At the company I work for we use subversion and TortoiseSVN to manage our
We use Subversion for source control and have implemented a pre-commit hook that checks
We use Subversion as our source control system and store the VisualStudio project files
We use Subversion for version control and Jira for tickets. All our commit messages
We use Subversion locally, and we're working on a project that uses a fork

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.