Pro Events addOn: event_post information not being pulled in by themes view.php
Permalink
I am using the Pro Events addOn on the following sitehttp://thebigshed.info/index.php?cID=125...
I have created a view.php inside my theme directory which includes
the problem is when I create an event, and then visit the event page none of the information event_post template gets pulled in, and I am left with a blank page.
The thing I find confusing at this stage is that if I stay on the same page and change the theme to any one the the default ones, then the event_post information is now visible.
Can anyone tell me what is missing from my theme's view.php, that it does not act like the standard, one-size-fits-all single_page container that I thought it was supposed to function as? (or am i missing something else entirely?)
many thanks : )
I have created a view.php inside my theme directory which includes
<div id="leftCol">
<?php
print $innerContent;
?>
</div><!-- end leftCol -->the problem is when I create an event, and then visit the event page none of the information event_post template gets pulled in, and I am left with a blank page.
The thing I find confusing at this stage is that if I stay on the same page and change the theme to any one the the default ones, then the event_post information is now visible.
Can anyone tell me what is missing from my theme's view.php, that it does not act like the standard, one-size-fits-all single_page container that I thought it was supposed to function as? (or am i missing something else entirely?)
many thanks : )
Hi ChadStrat,
I have tried clearing the cache with no avail.
And yes you are correct, I do have the all the correct theme information, I just posted the code the from the relevant div.
Also with reference to your answer in the Pro Events addOn help section.
"Standard practice is specific to "Main" and "Sidebar" area names. These are case sensitive."http://www.concrete5.org/marketplace/addons/proevents/questions-and-discussion/view-php-not-being-found-on-custom-theme/#179076
I am assuming you mean the names in the <?php tags rather than the names of the enclosing div?
I'm not entirely sure how this applies, (and I could easily be mistaken), but as far as I understood the MyTheme_directory/view.php page type~
its purpose it to replace the usual
with
thus replacing the editable area, with the php/html code contained within the blocks/content/templates/event_post/view.php file?
semantic idiosyncraticness aside, the mytheme/view.php is exactly the same as the darkchocolate/view.php
(unless you are saying the way I have named the enclosing div could be causing the problem?)
thanks again
I have tried clearing the cache with no avail.
And yes you are correct, I do have the all the correct theme information, I just posted the code the from the relevant div.
Also with reference to your answer in the Pro Events addOn help section.
"Standard practice is specific to "Main" and "Sidebar" area names. These are case sensitive."http://www.concrete5.org/marketplace/addons/proevents/questions-and-discussion/view-php-not-being-found-on-custom-theme/#179076
I am assuming you mean the names in the <?php tags rather than the names of the enclosing div?
I'm not entirely sure how this applies, (and I could easily be mistaken), but as far as I understood the MyTheme_directory/view.php page type~
its purpose it to replace the usual
$a = new Area('Main')
with
print $innerContent;
thus replacing the editable area, with the php/html code contained within the blocks/content/templates/event_post/view.php file?
semantic idiosyncraticness aside, the mytheme/view.php is exactly the same as the darkchocolate/view.php
(unless you are saying the way I have named the enclosing div could be causing the problem?)
thanks again
well, you still would need your event_post page type to have the appropriate divs and area names. I didn't know if you had made your own root level override for that page_type, and mistakenly mis-named the areas.
If I'm you, I roll back a bit, and step by step verify that the correct files are being used in fact.
use "<?php var_dump('TEST')?> in key locations such as the header, the view.php file, and the footer to verify that those files are in fact loading.
also, view source to see if there are any errors being tossed by something.
Or, additionally you can use chrome inspect console and reload the page to see if there are any javascript errors.
Chad
If I'm you, I roll back a bit, and step by step verify that the correct files are being used in fact.
use "<?php var_dump('TEST')?> in key locations such as the header, the view.php file, and the footer to verify that those files are in fact loading.
also, view source to see if there are any errors being tossed by something.
Or, additionally you can use chrome inspect console and reload the page to see if there are any javascript errors.
Chad
sorry if I am misunderstanding you here, but would you mind clarifying a few points (:
the main I am having trouble understanding is how the default themes manage to pull the information from your plugin, without the creation of any additional page types.
are you saying that when the plugin looks for a place to dump the events_post/view.php information, it looks for specific path in the html, rather than just placing the information within any area that has the
call?
the main I am having trouble understanding is how the default themes manage to pull the information from your plugin, without the creation of any additional page types.
are you saying that when the plugin looks for a place to dump the events_post/view.php information, it looks for specific path in the html, rather than just placing the information within any area that has the
<?php print $innerContent; ?>
call?
ps. i can confirm that the header/footer are definately loading, as I have my navigation/footer contents inside them, as they are used throughout my theme, and that these are being pulled when the page loads.
also please use the addon's support forum.
I had originally posted in there, but after thinking about the problem further and searching the forums, it seemed to me that my problem was not with the add on in particular, but more with my understanding of the way mytheme/view.php relates to the view.php files contained within the various plugins, and as such being a more general issue.
As this seemed to be a generally poorly understood topic, I thought the post would serve more use in the general forum. Hope thats cool (:
As this seemed to be a generally poorly understood topic, I thought the post would serve more use in the general forum. Hope thats cool (:
1. Clear browser and C5 cache
2. Simply Create a new theme page_type in your theme called event_post.php.
On another note, is that code " all" you have in your view file? Because you also need to include your header and footer in that file as well.
ChadStrat