Jump to content

tswalling

Members
  • Content count

    44
  • Joined

  • Last visited

1 Follower

Profile Information

  1. tswalling

    Overture / Google Adwords Reporting

    Still only planning. I'm working on a css template project using BTS with a few others right now among other things. This is still definitely something I plan to start work on but only when time permits. I'll keep people updated via this thread.
  2. tswalling

    STS OR BTS

    It won't be a nightmare for people who use either of these template mods. Especially the STS contribution. You're only editing 1 file for your layout! As far as waiting for an official template release that could be anywhere from 6 months to a year or longer.
  3. tswalling

    STS OR BTS

    I'm pretty sure that's just the javascript that oscommerce uses. The BTS mod doesn't use any javascript itself. At least none that I'm aware of.
  4. tswalling

    STS OR BTS

    FYI, I'm working with a few others on an all css layout for oscommerce. We are using BTS. If you're interested in following it or contributing we have a forum here: http://forums.eeweb.nl/
  5. tswalling

    STS OR BTS

    I favor BTS more because its closer to a true template system. STS relies more on parsing through your template file every time you display a page, inserting the osc code in the spots you designate. There are weaknesses in that which include more processing serverside. I don't think there have been any disussions about this and I'd like to see what other people think. BTS is more of a true template system because it takes the default osc layout code and puts into a template folder. I think it will be fairly close to what the template system will be for Milestone Release 3. The other advantage is that you will have more control on a per page level. STS will be supporting this soon and it requires less files to install so they both have their advantages. I don't think that BTS has any real disadvantages though. I would consider BTS a more solid solution to templates for osc while STS more of a plugin. People seem to be very happy with both as I've been following both threads and have used both myself. I decided to go with BTS though.
  6. tswalling

    Overture / Google Adwords Reporting

    Yes this is what I'd want people to do in order to setup the tool to look for a standard variable in the log files. If anyone visits the overture tutorial with the link I provided in the first post they can see an example of this. If people setup their tracking urls to be something like: http:///www.yourstore.com?ref=overture&keyword=design for each of their keywords then I'll know what to look for in the log files. At least this is they way I'm going to code it for now. I know I could make it more flexible but I'd like a standard to follow.
  7. tswalling

    Overture / Google Adwords Reporting

    Yes, I would be including that, but it would be a maual entry by the user. My post above was relating to what the code would generate in the report. I should have been more clear. There will be a few items that are required input in order to generate the true ROI.
  8. tswalling

    Overture / Google Adwords Reporting

    Yeah I'd like to take a good look at the code and features for both Adtracker and OSCaffiliate. I think the ROI per search term is important for determining how well your campaigns are going. Everyone should be doing this anyway, but saving time through a report would be great. To review it looks like some of the things we would want included include: (note: all of these numbers would be per advertiser, ie overture, google, etc) Overall Hits Hits per IP/User (useful to check for abuse) Hits per Search Term Purchases per IP/User (doesn't figure into ROI calculation but why not I guess) Purchases per Search Term (even if user leaves and purchases later) ROI per Search Term Overall ROI for Advertiser Sorting of these numbers by Date Range Just wanted to summarize some goals of the mod. Feel free to add more numbers. Before coding I'd like to have some requirements then plan out what will be included in what release, etc. -
  9. tswalling

    Overture / Google Adwords Reporting

    I've reviewed posts on the subject and have seen how OSCAffiliate could meet this basic need, but I think its valuable to have some overture/adwords specific reporting for this also. Things like breaking down number of visitors per search term, allowing the store owner to input their pay per click rate for each search term, then comparing the ROI for each of these search terms. I'm sure the affiliate mod could save some time, but I'm looking to create a specific solution for this need. Not everyone may want to install the affiliate mod just to get an idea of how their pay per click campaigns are going.
  10. I'd like to begin work on a few reporting tools for overture and adwords. Maybe start with some basic reporting to look at the visitor stats to find out number of visitors and what keyword they used to get there. Then move on to some other tools which help figure out your ROI. Since I don't have an active store or a current account with overture or google I'm looking for a few people who would be willing to test out any code I write. To test it locally, I'll most likely be manually inserting mock entries into my log files. People that are willing to test should have tracking urls setup in their overture accounts so that the reporting contribution can have a standard to look for. For an example for those who don't know what I'm talking about visit: http://www.content.overture.com/d/USm/ac/st/track.jhtml to view the flash tutorial regarding the subject. Some of this may just end up being an extension of the Ad Tracker contribution but I'll have to see. Any input on this subject is welcome.
  11. It looks like DIR_WS_TEMPLATES isn't defined in your configure.php. Did you double check that?
  12. I completely understand how your aim is simplicity. I only bring up including these ideas because I'm pretty sure people will be interested in having them and I'd hate to make a mod of a mod for it. This is of course your baby and I'm just throwing ideas out there that I think enhance it. Anyway... 2 more minor bugs with easy fixes: account_edit.php line 123 was: $javascript = 'formcheck.js.php'; should be: $javascript = 'form_check.js.php'; account_password.php line 68 was: $javascript = 'formcheck.js.php'; should be: $javascript = 'form_check.js.php'; This was breaking these files since the javascript was coming up missing.
  13. No need to be embarrassed about bugs. Coming up with a template system mod for oscommerce is no small task. The only way to make sure it works properly and bugs are found is to just release it and let people test it. Thanks for the info on the theme folder idea. I should have figured that out myself instead of taking up your time to explain it. I just wanted to make sure it wasn't a big task. I'm going to test the idea out to see how it works. One issue I do see is the stylesheet. It doesn't look like you are putting that in the template folder. Do you think this is something that should be moved into the template folder anyway? Also if this theme folder structure I've proposed works is it something you would consider adding to the core mod?
  14. Brenden I thought of one addition that would be super useful moving forward. How difficult would it be to create a new folder in the /templates/ directory which would house all of the current files there now? Call it /templates/default/ and then set a parameter in configure.php which would define the current theme as "default". I think this would be a great addition since it would allow users to easily create new themes in the template folder. This would let people work on them, test them out by changing the setting in configure, then changing it back if they don't like it. If this was in place I would be interested in writing a small admin mod which would store this template choice in the database. I don't want to turn this into a big project especially if you aren't envisioning this, but I think at least having seperate theme named folders in the /themes/ folder would be awesome. Let me know what you think.
  15. 2 Bug reports, fix for one of them Bug 1 On the checkout pages the NAVBAR_TITLE isn't being set properly so the text NAVBAR_TITLE is literally showing up in the page. I'm still familarizing myself with the code so not sure what's wrong here. I do know that that language file for this page defines two variables, NAVBAR_TITLE_1 and NAVBAR_TITLE_2. Not sure of the logic with sets NAVBAR_TITLE. Bug 2 + fix there is a missing definition in: /includes/filenames.php checkout process wasn't being defined so I couldn't finish my test order. The following code needs to be added and it then it will work fine. define('CONTENT_CHECKOUT_PROCESS', 'checkout_process'); and define('FILENAME_CHECKOUT_PROCESS', CONTENT_CHECKOUT_PROCESS . '.php'); I just followed the standard in the file and put each line in it's logical place. Brenden I just did a fresh install on my local machine just so I could test this mod since I'm very interested in it. If you need me to do any specific testing let me know. I'll continue to look for bugs.
×