When placing more than one "texteditor" (aka tinymce instance) type form field on an admin side form, only the last tinymce instance works properly.

Any instances placed before the last one have these problems: 1) When switching to visual mode, the text area looses all formatting and buttons. Switching back shows correct HTML/Text View. 2) The field acts as an updateable field (ie. turns orange).

I took a look at the jquery code in the form/text_area.tpl file. First thing I noticed was 'tinymce.remove();' was at the very top which appears that the second instance would kill the first instance, but removing it had no affect one way of the other.

One thing I did find is that the value for 'activeEditor' was the last tinymce instance when you clicked on the first. This would suggest to me that activeEditor should be defined. I tried a few solutions, but could not get any to work properly.

Does anyone have a fix for this or a suggestion of how to proceed? The extension I am working on really needs multiple instances of tinymce on the page. This problem appears to be one of the downsides of switching from ckeditor.

Don

Looking for developer help. I am working on a new extension and ran into a problem with the dispatch command.

In my extensions core file, I have the function: onControllerCommonSeoUrl_InitData(). I have a need for one page to execute a custom url different the the standard url output format generated by seo_url.php. This is the code I have:

public function onControllerCommonSeoUrl_InitData(){
                if (isset($this->baseObject->request->get['_route_'])) {
$parts = explode('/', $this->baseObject->request->get['_route_']);
if($parts[0] == 'my_page_name') {
  $this->request->get['m'] = $parts[1];
$this->request->get['y'] = $parts[2];
$rt = 'pages/XXXX/archive';
                                //name removed - don't want to say what the extension is yet

                                 unset($this->baseObject->request->get['_route_']);
                                 //this prevents the script in the base file (seo_url.php) from processing any other data
                                 
                                // The next two lines come from the end of seo_url.php       
//This line works
  $this->baseObject->router->resetController($rt);

                               // This is where the problem is...
  return $this->dispatch($rt,$this->request->get);


}else{

foreach ($parts as $part) {

                                 //continues ........
 

return $this->dispatch($rt,$this->request->get);
Dispatch does run but returns the correct layout for my page with blocks from the intended page and my index page.   

I tried inserting baseObject as you should in an extension core file:   
return $this->baseObject->dispatch($rt,$this->request->get);
This returns a blank page with the logged error:  error: AbanteCart core v.1.2.2 Call to protected method AController::dispatch()  from context 'ExtensionXXXXX'....

The page will load if I use the standard format non-seo url. It will also load if I use a RewriteRule in my .htaccess file (trying to avoid this). The values for dispatch route are correct ($rt = 'pages/XXXX/archive') and the values in the array are valid and correct. Values are correct in the block_layout table.

Any suggestions on what I need to do to get dispatch to properly run?

Hi,

Anyone know how I could get a second domain name to point to a specific page within AbanteCart without creating a second store?

I have an extension I am working on that I would like the option to have a secondary domain name or a sub-domain be able to point to it. The extension resides within the cart and does have its own path by way of controller access (index.php?rt=xxx/xxx) and seo access (/xxx). I can get a sub-domain to point to /xxx but of course get errors and it does not work so well. Ideally the second domain pointer would be an alias to the main domain but keep its identity.

Creating a second store means creating a whole new set of template files, which I don't want to do as the extension relies on the existing store template files and data.

I thought about the possibility of using .htaccess redirect but have not tried it yet. I have also thought about partially creating a second store to get the identity but using the existing templates but I am not sure if this will cause additional problems.

Anyone have any thought on how I might accomplish this?

Thanks

I am working on a new extension which has large presence on the admin side. As such I have a few pages using the listing grid functions. I am on my last section and I am having a problem with the $ID% value in the edit link being properly replaced. Instead of the the record set row value each link and grid row value is a sequential number starting at 1 and increasing to the amount of records. On top of that, if I change the order of the records, I get the same result with the numbering starting at one and progressing...the original number does not stay with the sorted value.

I have built several sets of pages using the listing grid and this is the first one I have seen this problem. All are structured the with the same code structure just replaced values. All data flows correctly from query to responses to controller except for this problem.

The correct record values are being added to the array in the results loop on response->rows[$i]['id'] = [my id value]  line on the response page. But somehow the values are not making it to the jgrid script. I have done all sorts of testing and can not find the problem.

Any suggestion of what may be causing this problem or where I should be looking?

Thanks in advance

I recently installed PayPal Express, set everything up and fully tested. Everything works except the checkout process seems to be out of order.

Normal process with credit cards and other payment methods: Cart -> Shipping -> Select Payment Option -> Confirm Order (and enter cc info) -> Success Page

The Paypal Express process is: Cart -> Select Payment Option -> Payment through Paypal -> Confirm Order Page -> Success

Shouldn't the Paypal Express process be the same as other processes?: Cart  -> Select Payment Option -> Confirm Order Page -> Paypal Payment - > Success

I have two concerns about the current process:

1) The current Paypal process relies on the user to click the confirm button on the confirm order page once returned from Paypal. I don't know about you, but a user (maybe an inexperienced user) might think they are done when they are done once payment is made to Paypal and not realize they need to click this final button.

2) The confirm order page gives the user the opportunity to make changes to their order, shipping options, and payment information. Shouldn't this be done before going to Paypal?

The current process actually hits PayPal twice, once after the payment option choice and once again after the confirm button is clicked. Granted, the actual checkout with Paypal takes place when the confirm button is clicked. If changes are made from the confirm order page they do reflect on the actual order record in both the cart and at Paypal. However, wouldn't it be more efficient to go to Paypal once the order is actually confirmed?

Just to see what would happen, I commented out the unction: onControllerPagesCheckoutPayment_ProcessData() in the core file and did follow the process of Payment -> Confirm -> Paypal. The only difference is that Paypal did not show the cart contents only the total. This is because the product data is not being sent to Paypal in the responses/confirm function. An easy fix.

The only thing I can figure is the designed process is intentional and there is good reason why the process is as it is. Please enlighten me or let me before I make changes to the extension.

Exactly what I have done. The only thing different is I changed the name of the Block name and title, which by all rights should not be an issue. I tried deleting the block and recreating it, but still the same. I also did not mention in the original post that there is no javascript/jquery added to the page to control the banners.

Incidentally I did get a warning message: 2014-11-21 18:55:36 - warning:  AbanteCart core v.1.1.9 Invalid argument supplied for foreach() in <b>/[cut]/admin/controller/pages/design/blocks.php</b> on line <b>553</b>.

I can't seem to post the code snippet, but $tpls is undefined as there is no /html_block folder in the file structure. Take at the /html_block reference in $tpls and $pos and the warning goes away. I do not believe this is a contributor to my problem as I created the block with and without the change and got the same result.

Is there a way I can influence which block template is used when the page is created? Perhaps in the database?

Thanks.

I got it to work by commenting out the following lines in cache.php

//if(!is_array($cache_files)){
   //$this->registry->get('log')->write('Cache directory is not accessible or writable.  Caching operation was skipped!');
//}