Publish 2 RSD projects for same...

User 2728698 Photo


Registered User
38 posts

Hello everyone. I tried to ask about this earlier but I don't think I explained myself very well / didn't ask the right question, so here I go again. Hopefully this makes more sense.

I have 2 RSD projects, because I needed to have more than 75 pages in my project. In all, I have a little over 90 pages. One project is the main website with the main pages, and the other project has pages for our products. I need to publish both of these projects onto my S-Drive Site so that I can send a link of the site to my boss to get approval/see what changes need to be made before I upload it onto our server. (My Coffeecup.com site is not the actual site.) For the most part everything works fine, but I have noticed that some things (like some images) do not have the correct breakpoints when I check out the site online. In my RSD project it looks fine and the Preview is perfect, but once I Publish it, it gets odd. I think (and please correct me if I am wrong about this) that the main.css is what is being messed up. I believe that one of the RSD projects is replacing the previous version of the CSS files when I publish them, which means that all of my styles for one project is all messed up.

Does anyone have any ideas or suggestions to work around this? This will also be helpful for when I finally upload the site to the server.
Monique
User 188640 Photo


Registered User
895 posts

You could use two different css folders. Leave the main site folder as css and rename the second as css2. Then you would have to change the links on the pages that have css2 to in the head section to reference the new folder name.

It would be a lot of work but with a text editor like Notetab++ you can do a find and replace.

Hopefully someone else has an easier solution but that should work if you can't find an easier way.

I don't know if you can rename the folder in RSD and have the head section links pick up on that because I haven't tried that. You may still have to manually rename the folder and links.
A Rose is Just a Weed in a Corn Patch!
User 2800147 Photo


Registered User
68 posts


Hello Monique,

I work the way you describe with several RSD projects (always carefully named incl. date in name) which I continuously save and back up.
Like you, I have a “main” RSD project. That is the only project I will make class changes too, which influences the css.
The secondary RSD projects are all copies from the original with most pages deleted, except main category pages to create space and thus share the original css. In these secondary projects I never make changes to the Class only the ID.
The breakpoints were set in the main RSD Project only. I make changes to secondary project pages by testing on a smaller breakpoints to see if the design needs adjustment, then I move to a higher breakpoint and make the adjustments there. That way I know the page displays right up the next smaller screen - breakpoint. (I hope I makes sense here). I don't ever add a new breakpoint.

I have no experience with the S-drive. I do FTP uploads to a server. It's important to save / export / upload the secondary projects first. Then you have to save / export / upload your main RSD project last. That way the main css file stays intact.

If the server send message “Do you want to replace this file with a newer file on server”or something to that effect , then you made changes on the secondary projects “Class”. I've learnt the hard way never to say yes, since that messes up the Main RSD Project and you will have to step back to older versions of your main project to correct the error.

It is a laborious way of working around a large website and makes adding new information tricky later on if the project needs maintenance updates. I'm still working on some fine tuning, but this is the website so far – www.jewelry-tutorials.com

The method above is only due to the page limit. For the most part RSD is a great website builder and really made building a responsive website so much easier.

I hope this helps your upload issue.

Kind regards,
Anne
titanium-implant-jewelry.com
jewelry-tutorials.com
drill-straight-tools.com
User 2728698 Photo


Registered User
38 posts

Ernie Hodge wrote:
You could use two different css folders. Leave the main site folder as css and rename the second as css2. Then you would have to change the links on the pages that have css2 to in the head section to reference the new folder name.

It would be a lot of work but with a text editor like Notetab++ you can do a find and replace.

Hopefully someone else has an easier solution but that should work if you can't find an easier way.

I don't know if you can rename the folder in RSD and have the head section links pick up on that because I haven't tried that. You may still have to manually rename the folder and links.


Thank you Ernie! I appreciate your response. From what I see, I have to change the folder name manually. I think your idea might be the best solition for my situation at the moment. I am going to give it a try and see what happens. Thanks again!

Monique
User 2728698 Photo


Registered User
38 posts

Hans & Anne wrote:

Hello Monique,

I work the way you describe with several RSD projects (always carefully named incl. date in name) which I continuously save and back up.
Like you, I have a “main” RSD project. That is the only project I will make class changes too, which influences the css.
The secondary RSD projects are all copies from the original with most pages deleted, except main category pages to create space and thus share the original css. In these secondary projects I never make changes to the Class only the ID.
The breakpoints were set in the main RSD Project only. I make changes to secondary project pages by testing on a smaller breakpoints to see if the design needs adjustment, then I move to a higher breakpoint and make the adjustments there. That way I know the page displays right up the next smaller screen - breakpoint. (I hope I makes sense here). I don't ever add a new breakpoint.

I have no experience with the S-drive. I do FTP uploads to a server. It's important to save / export / upload the secondary projects first. Then you have to save / export / upload your main RSD project last. That way the main css file stays intact.

If the server send message “Do you want to replace this file with a newer file on server”or something to that effect , then you made changes on the secondary projects “Class”. I've learnt the hard way never to say yes, since that messes up the Main RSD Project and you will have to step back to older versions of your main project to correct the error.

It is a laborious way of working around a large website and makes adding new information tricky later on if the project needs maintenance updates. I'm still working on some fine tuning, but this is the website so far – www.jewelry-tutorials.com

The method above is only due to the page limit. For the most part RSD is a great website builder and really made building a responsive website so much easier.

I hope this helps your upload issue.

Kind regards,
Anne


Thank you Anne! That all makes sense and in the furure I will do just the same, at least until RSD increases their page limit. But when I started I didnt think about the issues I might face down the rosd, I didn't think things thru and unfortunately I cannot make my projects like that at the moment. Perhaps in the future I will spend some time and fix my projects to function more smoothly like yours with all classes in the main RSD project. I greatly appreciate your detailed response. You definitely answered my question.
Monique
User 515127 Photo


Registered User
116 posts

This may not be completely relevant to your situation but for large (many page) projects, I chop them up into segments/sections based on focus or usage and put them into individual sub-domains.

For example - www (for point of presence and marketing pages) support. for customer support pages, siteadmin for dynamic content changes/additions/uploading of pictures, customer or client. for dashboards that include account info and order/payment histories that sort of thing - accounting for database reports of transactions and payments for the bookkeeper or management review.

Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.