Thread

Currently our IT has only a set amount of control over our servers. Our set up is that all three sites run on the same server. We set up EE and MSM on site one. Sites two and three are both redirecting via frame sets to folders set up on site one, which is not ideal but we are limited by IT control.

We seem to be having trouble with EE linking to template groups. Here is why I am thinking this is the case:

1) None of the configurations below will work when the stylesheet is set as css in EE template manager and linked in the blog group index as:

{stylesheet=blog_styles/reset}
{stylesheet="blog_styles/reset"}
{stylesheet='blog_styles/reset'}

2) None of the title permalinks will work they just direct to a 404 error

"{title_permalink='blog/press_view'}"

.

Not Found

The requested URL /index.php/blog/view/corson_engagement_portrait_session was not found on this server.

** Edit**
3)Using Firebug on Firefox I can manually change the path of the frame to view the pages within the group. In this case it is a “blog” group with a second blog_styles group that should be accessing those stylesheets that I mentioned earlier.

Yes, I am new to expression engine and this very well could be a rookie mistake. I have looked over a lot of the forum and tried various things. I found a work around for the stylesheets in putting them in the folder of the respective two sites (next to the /images folder) then just linking to them from the base root of the site (not ideal) but all my images are working.

What am I missing to cause these issues or could the frameset be the cause of this error?

Cheers

Bryce Pelletier
Creative Media

Hi, Bryce, welcome to the forums!

Unfortunately, with those Sites loading via Frames, I don’t think this is going to work out for you.  Are you able to load on a host with a more standard configuration?

One thing you can try is to go to Admin > System Administration > Output and Debugging and turn on “Force URL Query Strings”.  That may help.

Thanks!

Thanks Lisa. I had a feeling that this would be the answer. I couldn’t think of any way that would pass the information since the url is now different than the actual path to the pages. The “Force URL query strings” fix didn’t work. In fact it threw a different 404. Not sure which index.php it would be looking for since there are a half dozen, but this is the error.

Not Found

The requested URL /index.php was not found on this server.

I’ll consider this a dead topic unless someone has something creatively simple that would force EE to use the base path instead of the url to pass the new URL to the Frameset. I’ll have to see what corporate says about switching to a new server.

Thanks for your help in the matter.

Cheers

Bryce Pelletier

Hi Bryce,

Sorry we could not be more helpful!
Please post again with any future issues 😊

Best regards,
Barry