mark2

But the location of where the wordpress files are located on my server & the actual URL address are different, so that’s why I have 2 different urls in the settings

This is a fresh install.

Update # 2

I’ve fixed the broken permalinks issue… however, all urls are still going to https://www.example.com/sub/pageexample when it should be sub.example.com/pageexample

My URL settings in wordpress are:

WordPress Address (URL): https://www.example.com/sub (where the file are located on the server)
Sute Address (URL): https://sub.example.com (what I want the display URL for the site to be)

Anything I could be missing…?

Ahhhh… failed to do that.

Ok, I’ve now reset the permalinks, but now all the links are broken… When going to the site on the subdomain, sub.example.com I’m redirected to https://www.example.com/sub with all the links pointing to sub.example.com but they are broken… Anything I could be missing here?

Hmmm, I can’t seem to get it to work right.

I’ve found a great plugin that creates the drop down list that I can filter by category (Drop Down Post List), however I can’t seem to figure how to make the plug-in load an info box vs. jumping to the post.

Is it possible to modify the plugin, so it triggers GeoMashup info boxes instead of linking to the posts?
I’ve found this section of code within the plugin that I think deals with the linking to posts:

if ($ddpl_type == 'jump') {
		$t_out .= '<form class="ddpl-form" name="catform' . $catID. '" id="catform' . $catID. '" action="">';
		$t_out .= $ddpl_before_list;
		$t_out .= '<select name="jumpMenu' . $catID. '" id="jumpMenu' . $catID. '" onchange="MM_jumpMenu(\'parent\',this,0)">';
		if ($ddpl_default != '') {
			$t_out .= '<option value="">' . $ddpl_default . '</option>';
		}
		foreach ($post_list as $p) {
			$t_out .= '<option value="' . get_permalink($p->ID) . '">' . $p->post_title . '</option>';
		}
		$t_out .= '</select>';
		$t_out .= $ddpl_after_list;
		$t_out .= '</form>';

Would I be able to insert GeoMashup.clickObjectMarker() somewhere in there to trigger the infobox, or there much more req’d to do this?

As quickly as this problem appeared, it seems to have disappeared today… (knock on wood!)

I gave the hosting company a ring yesterday and explained my situation. They said they couldn’t find anything wrong, however I’m guessing they may have rebooted the server… who knows.

The site seems to working now. I’m almost certain it was something triggered on their end. I was making ALOT of updates to the site yesterday, so I’m guessing that had something to do with it.

Thanks for the link – I’ll run my site through that to see if anything pops up!

Still haven’t been able to crack this one… anyone have any suggestions?

I (finally) solved the problem!

Yes – it did have to do with the functions.php & the include…

I found this article which address the problem I was having with the Warning: include() problem.

I tried using include $_SERVER[‘DOCUMENT_ROOT’] solution instead of include() and that solved the problem. I can know access the admin panel & the site is functioning fine.

Thanks for your help with the issue dkotter, I appreciate it!

Just noticed something in the first error that appears when trying to log into the wp-admin page….

Warning: include(/usr/home/contract/public_html/newsite/newsite/wp-content/themes/kustom/config_files/content/sidebars.php)

The /newsite/ directory is in there twice… I’m thinking this could be the source of the problem. From what I’ve seen, I haven’t seen any duplicates of the “newsite/newsite/” in any of my files… What do you think could be triggering this?

I tried swapping with the full URL (https://www.contractsupply.ca/newsite/wp-content/themes/kustom/config_files/content/sidebars.php), but still showing the same errors….

I know it’s probably a small error that’s causing this, just a question of pinpointing it..

Yes, I think it’s something to do with my theme as well (it’s the Kustom theme)

Line 4183 has this:

include(get_absolute_url(get_bloginfo('template_directory').'/config_files/content/sidebars.php'));

And line 4184-4186 has this:

foreach($sidebars_names as $sidebarname) {
   register_sidebar(Array("name" => $sidebarname));
   }

I’m stuck at what I could change in this to fix the problem…

Hi dkotter,

Yes, I did follow the instructions referenced in that article, as well as the Changing_The_Site_URL article.

My siteurl value in the database is: https://www.contractsupply.ca/newsite (this is the directory that the wordpress files are located on my server)
and my home value is https://www.contractsupply.ca (the website URL)

I’ve copied the index.php & htcaccess file into the root directory & changed the line to :

require(‘./newsite/wp-blog-header.php’);

and htcaccess in the root directory to:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

The site works fine… the only issue is being able to access the admin…

***UPDATE ***

OK, I tried switching from the current theme to the default WP theme, and it’s now working…. so there’s something going on with my theme… Does anybody know where/how I’d be able to find where the broken reference(s) are?

Hi esmi,

I have reviewed the document (and a couple other related docs) and my problem is that I can’t seem to pinpoint the exact problem that’s effecting the site…

***Update***

I figured out a work-around fix that has temporarily solved my problem, but at the cost of the framework’s functionality…

As I mentioned in my previous posts, this theme’s framework CSS files are in PHP, that use dynamic values for certain CSS values.

My fix was to copy & paste the CSS source produced on my local (which was working) onto the CSS PHP files on the online versions (which was not working), effectively making them static.

See https://contractsupply.mark2marketing.com for a live version of the current work around

This seems to have solved the formatting problem, but I have now lost the ability to change the certain CSS properties through the framework’s admin…